VCGU
Vehicle Computational Gut Unit
A practical application of the CGU concept using real OBD-II telemetry, local trip logging, operating-state segmentation, and vehicle-specific contextual analysis.
Overview
Modern vehicles expose substantial internal telemetry, but it is usually viewed reactively: a warning code appears, a technician requests a value, or an app displays an isolated gauge.
VCGU records how multiple values behave together during real operating conditions. It separates trips into meaningful states, preserves each session, and looks for repeatable patterns before calling something unusual.
The first prototype proved that a local logger could read and preserve real vehicle telemetry and that post-drive analysis could reveal stable operating modes that were not obvious from a dashboard or a single average.
How It Started
VCGU began as a way to move CGU from a small environmental prototype into a complex mechanical system with existing sensors, feedback loops, changing loads, and multiple operating states.
The first phase was deliberately narrow: connect to the vehicle, capture a small set of signals, preserve them correctly, and determine whether useful contextual structure could be found.
Could the CGU principle help distinguish a vehicle’s normal internal patterns from meaningful change without pretending to replace diagnostics?
Architecture
Vehicle Signals
- RPM
- Speed
- Coolant temperature
- Engine load and throttle
Capture Layer
- OBD-II adapter
- Python logger
- Session timestamps
- Signal availability checks
Context Layer
- Startup / shutdown
- Moving / stopped
- Steady idle
- Accessory-load states
Analysis
- Cross-session comparison
- Vehicle-specific ranges
- Deviation review
- Charts and summaries
Development Timeline
Project start
VCGU was defined as Vehicle Computational Gut Unit and kept separate from virtual-CGU language.
Connection and capture
The logger established OBD-II communication and began preserving real signal data by session.
State segmentation
Stopped, moving, transition, startup, shutdown, and steady-idle behavior were separated for comparison.
Initial findings
Cross-signal analysis revealed repeatable stopped-idle modes with similar load, throttle, and manifold behavior.
Packaging and broader capture
The next step is a cleaner logger package, more sessions, automatic state segmentation, and controlled before/after comparisons.
Results and Current Boundaries
Real telemetry captured
The prototype successfully read and preserved RPM, speed, coolant temperature, and other available signals.
Repeatable states found
The vehicle showed stable operating distinctions that would have been obscured by one overall average.
Context requirement clarified
Drive phase alone was insufficient; short stops, steady idle, shutdown, and transitions needed separate treatment.
VCGU is an experimental logging and analysis workflow. It does not predict failure, replace diagnostic trouble codes, provide repair instructions, or generalize one vehicle’s baseline to every vehicle.
Project Materials
Capture
OBD-II logger, connection notes, signal definitions, and session schema.
Data
Sanitized trip CSV files and state-segmented samples.
Analysis
Cross-session scripts, charts, findings, and technical brief.
Add your final GitHub, ZIP, diagram, video, or document links here only after each public package has been reviewed and sanitized.