Where is Vehicle Telemetry when you really need it

Quick answer: it’s right there !! until you need it

Let's take my use case, my SUV occasionally throws a fault code “Air suspension malfunction” on a trip. The car is in warranty so I can be assured it will be fixed. Yes, that’s what one would think Right! WRONG!

Between the malfunction error and booking appointments with the dealership multiple Key-on — Key-off events happen and or a number of drive cycles which could evaporate the code or if not the code then associated conditions.

Here is an example I get “Air suspension malfunction light”. It is triggered by sensor throwing fault over N drive cycles. Now there will be other sensors that are keeping track of what was happening with associated systems when the error occurred. Now when I reach the dealership when they scan the car no code is found as associated conditions have subsided and code was deleted from the memory. This is the only plausible explanation based on multiple visits to the dealership that have resulted in! Nothing!

I got a better glimpse at the problem recently and an idea to solve it. While working with an automotive service provider, the plan was to make a mobile technician retrieve the DTC code upon arrival. Well, there are multiple problems with that approach :

1. Key-off event and code is gone
2. Mobile technician reaching the site without knowing what to bring or bring everything, there could be a 2nd trip

Solution :

1. Based on DTC code transmit the code and associated relevant data to the cloud
2. The trigger API call to the service provider with that data
3. The service provider system analyzes incoming data and proposes possible solutions
4. The technician arrives at the vehicle, with a better understanding of the issue
5. Happy customer