Not every ECU software question is an emissions question. Many claims concern vehicle defects, component damage, maintenance models, regeneration strategies or systematic behavior after software updates.

43IT investigates whether the cause lies in ECU code, calibrations, diagnostic data, EEPROM content or the interaction between software and vehicle operation.

Examples

• DPF regeneration strategy and DPF load models
• Catalyst aging, component protection and thermal management
• Oil-quality models, maintenance counters and service logic
• SCR dosing, heating and diagnostic thresholds

Our contribution

We translate technical implementations into a robust explanation of vehicle behavior. We can compare individual vehicles, ECU variants, software versions or larger data sets.

The goal is not an abstract description of the system, but a clear answer to the concrete dispute question: what software logic exists, when is it active, what technical effect does it have and how reliably can that effect be shown?

Typical deliverables

• Technical short assessment for early case evaluation
• Structured analysis reports and diagrams
• Function descriptions and data-flow analysis
• Comparison tables with affected variants and software versions
• Input for disclosure requests
• Proposals for measurements and vehicle testing
• Test data analysis and interpretation
• Support for expert meetings or hearings.

We distinguish carefully between observed implementation, technical effect and legal assessment.