Case studies

Two programmes, without the names.

These examples describe experience from anonymised validation projects. Figures are rounded. No names of customers, products or partners.

Case 01

Full in-vehicle traffic capture, then the same scope on the bench at lower cost

Problem

Equipping vehicles for full traffic capture was expensive, slow to set up and heavy to install. Space, power and coverage inside the vehicle were the limiting factors.

Project experience

The work began with a few weeks on the real constraints. A modular real-time capture setup followed. It converted every relevant vehicle interface into an IT-compatible format without disturbing the vehicle network. Source and time information stayed intact with high fidelity. Storage remained optional because it drives a major share of cost. Copy stations, encryption, and trigger- or event-based trace selection were part of the scope.

Rollout

The customer sourced the equipment directly. Systems were running four to six weeks after the devices arrived on site, with expert engineering support.

Remote operation

The setup supported remote diagnostics, remote configuration and remote flash updates of the capture systems.

Scale

Several hundred vehicles were equipped. Several dozen had full trace capture. The rest used a lighter specification.

Next step

Next, the customer extended the setup to static test benches. Bench-appropriate equipment provided the same scope, format, depth and interface coverage at a considerably lower cost. Depending on the component, it was typically 30 to 60 % lower.

Result

Coverage, space and power limits were resolved. The setup can be repeated and grows with the fleet.

Several hundredvehicles equipped
4 to 6 weeksfrom delivery to running systems
Considerably lowercost per bench
Most of the cost sits in two choices: the equipment grade for each place and the amount of storage.
Case 02

A validation setup for a vehicle architecture that did not exist yet

Problem

The customer had to validate an architecture before any real vehicle existed. The required scope was 150 to 180 % of the brand's largest vehicle.

Project experience

The same modular approach was scaled to full trace capture across all communication interfaces. The network and ECU interactions remained unaffected.

Added value

Diagnostic information helped pinpoint problems faster, including cabling faults. Abnormal events were recognised during the run. Live monitoring operated during capture, independently of full trace storage.

Cabling faults

Cabling faults were found within minutes by a routine check.

Same data everywhere

Resolution, fidelity and format were identical from vehicles, simple test benches, partial systems and the full lab car.

Result

Repeatable tests let the customer reproduce complex problems and give developers the data they need for a fix. Fixes were verified in days instead of weeks or months.

150 to 180 %of the brand's largest vehicle
Minutesto find cabling faults
Daysto verify a fix
When the data is the same in the car and on every bench, problems can be reproduced and fixes tested quickly.
Track record

Where this approach has been used.

These examples draw on experience from validation projects at German and international OEMs. Several hundred vehicles used this approach to data capture.

The experience comes from the founder's earlier roles and from delivery by partners.

Bring us the interface that does not fit.

Tell us the constraint that is blocking the next test phase. We will say within one call whether we can help.