Blog
  • VehicleOS

  • AI

  • OBD-II

  • Automotive

What if your car could carry part of the intelligence of a workshop's diagnostic tools?

VehicleOS: el diagnòstic intel·ligent que el teu cotxe mereix — comparativa amb eines de taller

A while ago, a client asked me for a PLC. And that got me thinking: a modern car is not just an engine. It's a network of ECUs, sensors, communication buses and thousands of parameters. And OBD-II is only the entry door.

That's why I'm building VehicleOS. The idea is to use AI to go far beyond "Code P0401 detected".

VehicleOS aims to: · Discover which ECUs are available. · Read the data they can provide. · Analyse parameters in real time. · Use AI to interpret the information. · Detect anomalous behaviour. · Explain what may be happening in plain language. · Build a digital profile of the vehicle.

With one fundamental rule: READ-ONLY. VehicleOS can read and interpret; it never modifies the vehicle's behaviour.

The architecture is: CAR → OBD-II → ECU → DATA → AI → INFORMATION.

I'm not trying to replace the manufacturers' official tools. But I am exploring something different: can an AI learn how a vehicle works just by observing and correlating its data? If the answer is yes, we could be looking at a new generation of automotive diagnostics.

This is VehicleOS: vehicleos.serverscel.com · coche.serverscel.com. The car already has the data. Now we're trying to teach the AI to understand it.

BlogBack to the CV
§

Contact — end of file

Shall we build something together?

Actively looking for a full-stack developer role (React · Next.js · NestJS) and open to freelance projects. Write to me and I'll reply the same day.

[email protected]+34 626 654 270Download CV (PDF)