TraceSpeak Fleet · Fleet data Available for pilots

Every fleet issue, answered.

TraceSpeak 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.

TraceSpeak Fleet, built on TraceSpeak Core Driver reports, software and hardware variants and diagnostic readouts flow into TraceSpeak Fleet. Vehicle logs are decoded by TraceSpeak Core, which feeds Fleet. Out come issues grouped by signature, the affected vehicles and the top suspect ECU. Engineers ask the Testradamus agents about correlations across the fleet. TraceSpeak Core TraceSpeak Fleet Driver reports SW & HW variants Readouts Vehicle logs notes and tickets per vehicle, per flash DTCs for every ECU decoded by Core Issues Affected vehicles Top suspect ECU grouped by signature and where it never happens implicated or cleared ACROSS THE FLEET Ask Testradamus
Built on TraceSpeak CoreCore decodes every vehicle’s data and detects anomalies and vehicle states. Fleet connects them across the whole fleet.Explore TraceSpeak Core →

What it solves

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? Meanwhile most of the fleet’s data is never checked at all.

TraceSpeak Fleet checks every vehicle and answers three questions for every issue:

  1. What happened, and on which vehicles? The chain from trigger to symptom, on every vehicle with the same signature.
  2. On which software and hardware? Where the issue appears, where it never does, and since when.
  3. Whose issue is it? The top suspect ECU, with repro steps for its owner.

How it works

Core detects. Fleet connects every vehicle to the right team.

01

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.

02

Finds issues, reported or not

TraceSpeak Core checks every wake-up and every drive against your network description. Fleet matches driver reports and tickets to what the data shows.

03

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.

04

Hands the issue to the right team

A package with the trace window, readouts and repro steps goes to the ECU’s owner, or to TraceSpeak CT for reproduction on HiL. Nothing else leaves your network.

Testradamus in Fleet

Agents that know every vehicle in your fleet.

The Core agents explain what happened inside one vehicle. Fleet adds three agents that look across all of them: which vehicles, which software and hardware, and whose issue it is.

Issue Matcher

Matches driver reports and tickets to what the data shows, and groups every vehicle with the same signature into one issue, reported or not.

Variant Correlator

Correlates each issue with software and hardware combinations, flash dates and mileage: where it appears, where it never does, and since when.

Owner Finder

Checks every candidate ECU, finds the software change that brought the issue in, and hands the issue to its owner, or to TraceSpeak CT for reproduction on HiL.

Ask Testradamus · illustrative

One driver’s note. Five vehicles. One answer.

A driver reports a warning. The Fleet agents check the whole fleet and come back with the vehicles, the software and the owner.

Testradamus · TraceSpeak Fleet
A driver reports: “The HV warning came on when I unlocked the car.” Is it one vehicle?

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.

5 vehicles1 issuegateway software B 21.5-rc.4illustrative

Underneath · what the agents checked

  • Issue Matcher: matched the driver’s note to the HV warning at unlock and found the same signature on 4 more vehicles
  • Variant Correlator: all 5 run the new gateway software; none of the other vehicles show it
  • Core agents: traced the warning to the power mode signal the gateway sends at wake-up
  • Owner Finder: implicated the central gateway, cleared the hybrid controller, and attached the repro steps

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 issueWhat 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 TraceSpeak CT: reproduced on HiL, suspect commit ranked
When there is no issueWhat 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

Who it’s for

One fleet, four teams.

Fleet & validation managers

Every issue across the fleet in one view, with the vehicles and software it affects.

ECU owners & suppliers

Only the issues that are really yours, with the trace window and repro steps attached.

Vehicle & integration engineers

The chain from trigger to symptom across ECUs and buses, from data you already log.

Team leads & management

Miles per software and hardware combination, and which issues stand between you and a release.

See Fleet on your own data.

We will show TraceSpeak Fleet on a simulated fleet, then on the logs your vehicles already record.