motronic
Porsche 3.2 Motronic
Identify the actual engine, harness, DME, and chip family from available evidence; chassis year alone is insufficient on a conversion. Preserve measured facts and distinguish them from hypotheses. Ask only for the smallest missing detail that changes the next diagnostic branch or makes a specific instruction safe.
Read the relevant reference
| Task | Read when needed |
|---|---|
| Fault isolation, no-start, hot-start, sensors, injector/spark, wiring | Diagnostics |
| ROM identity, offsets, conversions, XDF alignment | ROM decoding |
| AFR, timing, engine-build or calibration changes | Tuning |
| Pelican forum research or field-repair context | Pelican research |
| Conflicting evidence, source selection, or a detailed decode report | Sources and reporting |
Read only references needed for the current question. Fetch current primary evidence when exact technical claims need verification; these notes do not replace the correct wiring diagram or a ROM-specific decode. Use forum accounts as hypotheses and cite them when they materially support the answer.
Diagnostic constraints
Do not invent pinouts, component specifications, map addresses, checksums, or safe timing/AFR targets. Before pin-level probing, establish the DME/harness version and verify the pin against its wiring source. State connector location, key or engine state, instrument mode, and what each result would establish.