Software development for: Automotive From ECU to evaluation
Hardware-related software for control units, tools for the application of calibration data and data evaluation in production and supply chain. We work where the vehicles are created – in the Stuttgart and Sindelfingen area.
| Parameters | Old | New | Δ |
|---|---|---|---|
| KF InjTiming | 1,240 | 1,265 | +0,025 |
| KL BoostLim | 1 820 | 1 780 | −40 |
| KF EGR Rate | 0,318 | 0,402 | +0,084 |
| KL TempDerate | 108,0 | 108,0 | ±0 |
Three fields in which we work in the automotive environment
Not all of this needs every project. But the connection is the point: Anyone who knows the control unit software also understands the data it generates.
- Embedded C for ECUs
- CAN, CAN-FD and Automotive Ethernet
- Diagnosis of control unit communication
- Bus and network analysis
- Control of hardware I/O
- Tools such as CANoe and CANalyzer
- A2L, HEX, DCM, CDFX and S-record
- Versioning of calibration stands
- Parameter comparison of two stands
- Reviews with audit trail
- Limit test and monotony
- Gradients and saddle points in characteristic maps
- Evaluation of production and measurement data
- Predictive maintenance
- Transparency of supplier chains
- Knowledge graphs for component relationships
- RAG on technical documentation
- Operation possible in your own data center
- Versioning instead of file names – Every change is associated with a person, a time and a reason.
- Diff at parameter level – Two stands on A2L and HEX level, with old and new value and delta.
- Reviews with proof – Four-eyes principle on the single parameter, complete audit trail, verifiable release.
- Automatic plausibility check Limits, monotony, gradients and saddle points are checked before anyone releases.
- The data stays in the house – Operation on-premise or in the private cloud, access via Entra ID, SAML or OIDC.
More about the background in the article Calibration data management with versioning, reviews and AI assistance.
Why automotive projects run differently
Four boundary conditions that shape every project in this industry – and that explain why generic software often does not wear here.
In the middle of the automotive cluster
Between Stuttgart, Sindelfingen and Böblingen, there is a density of vehicle development that is so rare: manufacturers, development centers, Tier 1 suppliers, test benches and engineering service providers in a confined space. Our embedded projects run right there.
This is more than a location advantage on paper. Control unit work can only be done remotely to a limited extent – at some point someone has to stand at the test bench, read a bus protocol or measure it in the vehicle. If the way there takes forty minutes instead of a flight, it changes the timing of a project noticeably.
At the same time, the region is an environment where technology is taken seriously. Anyone who performs here with half-knowledge about on-board networks is back outside after the first appointment. This is exactly why we write on this page about formats and procedures instead of keywords.
- Short distances to test bench and vehicleOn-site appointments are plannable and not the exception.
- Specialists from the regional environmentWe hire embedded developers in the Stuttgart and Sindelfingen area – people who come from the industry.
- Coordination without friction lossesTechnical clarification with your engineers works faster at the table than over three ticket systems.
- Initial consultation free of charge and without obligation
- Also suitable if only a procedure should be clarified
- On request with a view to your existing tool chain