Model, engine, year, ECU type and HW/SW numbers if available.
Identify the control unit
Identify the ECU type and describe it correctly in a request
The ECU type often decides which file service provider fits a job. It is important to separate ECU manufacturer, ECU family and concrete variant.
What you need
Prepare the request faster
Original file, available file, read method, tool and anything that is uncertain.
Requested service, fault codes, symptoms, logs and relevant hardware changes.
Practical problem
Do not confuse manufacturer, family and variant
Bosch is a manufacturer, EDC17 is a family and a concrete variant can still have project-specific differences. Businesses should collect available evidence instead of guessing.
If the ECU type is unknown, the request can still be useful. State the uncertainty openly and include tool outputs or file information.
Preparation
Include these details in the request
check diagnostic device or reading tool
State it clearly so providers can assess it.
document label or casing information
State it clearly so providers can assess it.
save software ID and project information
State it clearly so providers can assess it.
state examples such as Bosch EDC17, MD1, MG1, Simos, Delphi or Denso clearly
State it clearly so providers can assess it.
mark uncertain details explicitly
State it clearly so providers can assess it.
include the file if the provider should help identify it
State it clearly so providers can assess it.
ECU Jobs role
Platform, not in-house file service
ECU Jobs does not create the file itself. The platform helps present the job clearly to professional file service providers and makes offers comparable.
More help
Relevant next steps
These pages help prepare the request further or start directly.
Request help overview
Relevant next step for this request.
Request help overviewECU overview
Relevant next step for this request.
ECU overviewBosch ECUs
Relevant next step for this request.
Bosch ECUsSimos ECUs
Relevant next step for this request.
Simos ECUsDelphi ECUs
Relevant next step for this request.
Delphi ECUsDenso ECUs
Relevant next step for this request.
Denso ECUsWorkshop practice
When the ECU label is not enough
An ECU label can be useful, but it is not the whole identification story. A housing may have been replaced, a used unit may have been fitted, or the visible number may not describe the software actually inside the control unit. That is why a request should combine label information with diagnostic output, read-tool data, file metadata and vehicle context. For example, Simos as a family tells a provider something different than simply Continental, while Bosch MD1 and MG1 point to different technical expectations than older EDC families. If the workshop is unsure, the request should preserve that uncertainty. A professional provider can often work with uncertainty when the evidence is attached; guessed certainty is harder to correct later.
Practical detail
Separate ECU manufacturer, family and exact variant
Bosch is a manufacturer, EDC17 is a family and the concrete variant still depends on vehicle, HW/SW numbers and file. Collect diagnostic output, tool information, label photos, software ID and project details. If uncertain, say so clearly.
More topics
Related request help
More pages help prepare file service requests more completely.
FAQ
Frequently asked questions
Is ECU manufacturer enough?
Usually no. Bosch or Denso alone does not define family, variant and software version.
What if the ECU type is uncertain?
Mark it as uncertain and include tool output, photos, file data or HW/SW numbers.
Can a provider help identify the ECU from the file?
Often yes, if the file and project details are available.
Why not link non-existing ECU detail pages?
The page should only guide users to existing helpful pages.
Which ECU examples are common?
Bosch EDC17, Bosch MD1, Bosch MG1, Simos, Delphi and Denso are common in requests.
ECU Jobs
Post a better request
Use the prepared details and post the file service request free of charge and without obligation.
