DOI: 10.11583/dtu.30483005.v1
title: The Kidmose CANid Dataset (KCID)

description: Kidmose CANid Dataset (KCID)The <b>Kidmose CANid Dataset (KCID)</b> contains CAN bus data collected by Brooke and Andreas <b>Kidmose</b> from 16 different drivers across 4 different vehicles. This dataset is designed to support driver identification and authentication research.The term "CANid" reflects the dataset's dual purpose: data collected from the <b>CAN</b> bus for driver <b>id</b>entification research.VEHICLESThe dataset includes data from four different vehicles across various manufacturers and model years:<b>2011 Chevrolet Traverse</b> - 5-door full-size SUV crossover, AWD, 8 drivers (8 unique drivers in single-driver traces; 1 additional driver in a mixed trace)<b>2017 Ford Focus</b> - 5-door compact station wagon, FWD, 4 drivers<b>2017 Subaru Forester</b> - 5-door compact SUV crossover, AWD, 6 drivers (6 unique drivers in single-driver traces; 3 additional drivers in mixed traces)<b>2022 Honda CR-V Touring</b> - 5-door compact SUV crossover, AWD, 1 driver<i>Note:</i> The number of drivers includes volunteer drivers whose data was captured in single-driver traces, where we know who was driving at all times. We exclude volunteer drivers whose data is only available in mixed traces because we do not know when each specific driver was actually operating the vehicle.DRIVERSThe dataset includes 16 drivers across different demographic categories:<b>Male Drivers:</b><b>Under 30 years:</b> 4 drivers ("male-under30-1" through "male-under30-4")<b>30-55 years:</b> 4 drivers ("male-30-55-1" through "male-30-55-4")<b>Over 55 years:</b> 3 drivers ("male-over55-1" through "male-over55-3")<b>Female Drivers:</b><b>All ages:</b> 5 drivers ("female-all-ages-1" through "female-all-ages-5")<i>Driver Directory Structure:</i> Driver identifiers are used as directory/folder names. Within each directory, you will find traces collected from that particular driver, with additional information (location, data collection method, etc.) specified in the filename.<i>Note:</i> We use "unknown driver(s)" in directory names when we know that one or more volunteer drivers was operating the vehicle, but we cannot identify who was driving or when. We used a standalone data logger for some data collection sessions. If we failed to download the data and clear the logger's memory before switching drivers, this resulted in mixed traces and, occasionally, "unknown driver(s)" entries. Unfortunately, some of our volunteer drivers were short-term visitors, so we did not have the opportunity to redo their traces as single-driver traces.LOCATIONSData collection took place across multiple locations:<b>DK</b> - Denmark<b>USA</b> - United States of America<b>FL</b> - Florida<b>NE</b> - Nebraska<b>NE-to-FL</b> - Trip from Nebraska to Florida<b>TN</b> - Tennessee<b>TN-to-NE</b> - Trip from Tennessee to NebraskaLocation codes appear in filenames (e.g., <i>USA-FL-CANEdge-00000001.mf4</i> indicates data collected in Florida, USA).DATA COLLECTION METHODSThree different data collection methods were employed:<b>CANEdge</b> - CSS Electronics CANEdge2: Standalone data logger that connects to the OBD-II port and logs to an SD card<b>Korlan</b> - Korlan USB2CAN: CAN-to-USB cable connecting the vehicle's OBD-II port to a laptop<b>Kvaser</b> - Kvaser Hybrid CAN-LIN: CAN-to-USB cable connecting the vehicle's OBD-II port to a laptopThe data collection method is indicated in filenames (e.g., <i>USA-FL-CANEdge-00000001.mf4</i>).FILE TYPESThe dataset provides data in three formats to support different use cases:<b>.mf4 (MDF4) Format:</b> Measurement Data Format version 4 (MDF4)Binary format standardized by the Association for Standardization of Automation (ASAM)<b>Advantages:</b> Compact size, popular with automotive/CAN tools<b>Use case:</b> Native format from CSS Electronics CANEdge2<b>Reference:</b> https://www.csselectronics.com/pages/mf4-mdf4-measurement-data-format<b>.log Format:</b> Text-based log format<b>Compatibility:</b> Linux SocketCAN can-utils<b>Advantages:</b> Compatibility with SocketCAN can-utils; if a .log file is replayed, then data can be captured and monitored using Python's python-can library<b>References:</b> https://github.com/linux-can/can-utils, https://packages.debian.org/sid/can-utils, https://python-can.readthedocs.io/en/stable/<b>.csv Format:</b> Text-based comma-separated values (CSV) format<b>Advantages:</b> Easy to load with Python using the pandas library; easy to use with Python-based machine learning frameworks (e.g., scikit-learn, Keras, TensorFlow, PyTorch)<b>Usage:</b> Load with Python pandas: pd.read_csv()<b>Reference:</b> https://pandas.pydata.org/SPECIALIZED EXPERIMENTSThe KCID Dataset includes five specialized experiments:<b>Fixed Routes Experiment</b><b>Vehicles:</b> 2011 Chevrolet Traverse, 2017 Subaru Forester<b>Drivers:</b> male-30-55-3, male-30-55-4, male-over55-1, female-all-ages-1, female-all-ages-2, female-all-ages-5<b>Location:</b> Florida, USA (specific routes)<b>Data Collection Methods:</b> CSS Electronics CANEdge2, Kvaser Hybrid CAN-LIN<b>Purpose:</b> Capture CAN traces for specific, mappable routes; eliminate route-based variations in driver authentication data (e.g., low-speed local routes vs. high-speed long-distance routes)<b>OBD Requests and Responses Experiment</b><b>Vehicle:</b> 2011 Chevrolet Traverse<b>Driver:</b> female-all-ages-5<b>Location:</b> Florida, USA<b>Data Collection Method:</b> CSS Electronics CANEdge2<b>Purpose:</b> Capture OBD requests and responses Arbitration IDs: <i>Requests:</i> 0x7DF, <i>Responses:</i> 0x7E8<b>Tire Pressure Experiment</b><b>Vehicle:</b> 2011 Chevrolet Traverse<b>Driver:</b> female-all-ages-5<b>Location:</b> Florida, USA<b>Data Collection Method:</b> Kvaser Hybrid CAN-LIN<b>Purpose:</b> Capture normal and low tire pressure scenarios<b>Applications:</b> Detect tire pressure issues via CAN bus analysis; develop predictive maintenance strategies<b>Driving Modes and Features Experiment</b><b>Vehicle:</b> 2017 Ford Focus<b>Driver:</b> male-30-55-1<b>Location:</b> Denmark<b>Data Collection Method:</b> Korlan USB2CAN<b>Purpose:</b> Capture different driving (and non-driving) modes and features<b>Examples:</b> gear (park, reverse, neutral, drive, sport); headlights on/off<b>Stationary Vehicles Experiment</b><b>Vehicles:</b> 2024 Chevrolet Malibu, 2025 Toyota Corolla<b>Driver:</b> N/A (vehicles remained stationary)<b>Location:</b> Florida, USA<b>Data Collection Method:</b> Kvaser Hybrid CAN-LIN<b>Purpose:</b> Capture CAN bus traffic from very new, very modern vehicles; identify differences between an older vehicle's CAN bus (e.g., 2011 Chevrolet Traverse), and a newer vehicle's CAN bus (e.g., 2024 Chevrolet Malibu)ADDITIONAL DOCUMENTATIONEach "specialized experiment" directory contains a detailed README.md file with specific information about the experiment and the data collected.RESEARCH APPLICATIONSThis dataset supports various research areas:Driver authentication, driver fingerprintingBehavioral biometrics in the automotive domainVehicle diagnostics and predictive maintenanceMachine learning in the automotive domainCAN bus analysis and reverse engineeringCITATIONIf you use the Kidmose CANid Dataset in your research, please cite appropriately. Citation information will be updated when our paper is made available as a preprint and when our paper is published in a peer-reviewed venue.<b>Article Citation:</b><b>APA Style:</b> Kidmose, B. E., Kidmose, A. B., and Zou, C. C. (2025). A critical roadmap to driver authentication via CAN bus: Dataset review, introduction of the Kidmose CANid Dataset (KCID), and proof of concept. {url}<b>MLA Style:</b> Kidmose, Brooke Elizabeth, Andreas Brasen Kidmose, and Cliff C. Zou. "A Critical Roadmap to Driver Authentication via CAN Bus: Dataset Review, Introduction of the Kidmose CANid Dataset (KCID), and Proof of Concept." 2025. {url}<b>Chicago Style:</b> Kidmose, Brooke Elizabeth, Andreas Brasen Kidmose, and Cliff C. Zou. "A Critical Roadmap to Driver Authentication via CAN Bus: Dataset Review, Introduction of the Kidmose CANid Dataset (KCID), and Proof of Concept." (2025). {url}<b>Dataset Citation:</b><b>APA Style:</b> Kidmose, B. E. and Kidmose, A. B. (2025). Kidmose CANid Dataset (KCID) v1 [Data set]. DTU Data. {url or doi}<b>MLA Style:</b> Kidmose, Brooke Elizabeth and Andreas Brasen Kidmose. Kidmose CANid Dataset (KCID) v1. DTU Data, dd Month 2025. {url or doi}<b>Chicago Style:</b> Kidmose, Brooke Elizabeth and Andreas Brasen Kidmose. Kidmose CANid Dataset (KCID) v1. DTU Data, 2025. {url or doi}<br>