Testradamus Fleet Preview in Novi, MI · 27–29 October
Every fleet issue, answered.
Testradamus Fleet checks the data from every vehicle in your validation fleet against your network description. For every issue it tells you what happened, on which vehicles and software, which ECU is the top suspect, and how to reproduce it. Every answer comes with the evidence behind it.
The problem
The fix takes a night. Finding whose fix it is takes weeks.
A driver reports a warning light. The log is attached the same day. Then the issue travels from team to team: is it our ECU? Which software was on board? Did other vehicles see it? Each stop takes days. Meanwhile most of the fleet’s data is never checked at all.
What Fleet answers
Ten answers for every issue. Two for every mile.
Each answer comes with the raw data and a graphic, so your engineers can check it in a minute.
| When there is an issue | What Fleet shows |
|---|---|
| What actually happened? | The chain from trigger to symptom, across ECUs and buses |
| When did it happen? | The exact moment and the vehicle state: wake-up, driving, parked |
| On which vehicles? | Every vehicle with the same signature, not only the one that reported it |
| Which ECU is the top suspect? | Every candidate checked at once: implicated, cleared, or not enough data |
| On which software and hardware? | The combination of ECU versions where it appears, and where it never does |
| Since when? | The first occurrence, aligned to each vehicle’s flash date |
| Can it be reproduced, and how? | Repro steps taken from the data, ready for another vehicle or a HiL |
| Does the vehicle recover, and how? | By itself, after a restart, a DTC clear or a reflash |
| Which ECU change introduced it? | The software change that brought it in, with before-and-after evidence |
| Which commit? | With Testradamus CT: reproduced on HiL, suspect commit ranked |
| When there is no issue | What Fleet shows |
|---|---|
| How many miles on this software and hardware? | Miles, hours and wake-ups per combination, counting only fully logged miles as evidence |
| How many miles per vehicle? | Each vehicle’s history across combinations |
How it works
From every vehicle to the right team.
Reads every vehicle
Logs, diagnostic readouts and DTCs for all ECUs, mapped to the build and hardware variant. Works with the data loggers you already have.
Finds issues, reported or not
Every wake-up and every drive is checked against your network description. Driver reports and tickets are matched to what the data shows, so related reports become one issue.
Checks every candidate ECU at once
Each one is implicated, cleared, or marked “not enough data”, with the frames that prove it. Clearing an ECU saves a team as much time as implicating one.
Hands the issue to the right team
A package with the issue’s trace window, readouts and repro steps goes to the ECU’s owner, or to Testradamus CT for reproduction on HiL. Nothing else leaves your network.
Local, like every Testradamus product
Runs inside your network on your own hardware.
Example · illustrative
One driver’s note. Five vehicles. One answer.
No. Fleet finds the same signature on 5 of the 8 vehicles with the new gateway software, and on none of the others.
Top suspect: the central gateway. It sends the power mode before it has received it. The hybrid controller raised the warning and is cleared: it reacted as specified.
Repro: park for 2 hours, unlock, record the first 100 ms.
Demo & early access
See Fleet live in Novi.
We show Testradamus Fleet for the first time in Novi, Michigan, 27–29 October, at hall ATXNA, stand S5. Book a slot, or join early access and we will show it to you on your own data.
In the meantime, the Testradamus CT demo shows the same core on HiL test data.