Change SOI (Start of Injection) timing in degrees, not percent — the map you want is DAMOS folder InjCrv_MI1 / map InjCrv_phiMI1Bas on EDC16/17/MD1. The SOI map is independent of fuel amount, so degrees give exact efficiency math: 1 degree ≈ 1% efficiency on closed-combustion diesel engines. Keep changes to +1 to +2 degrees maximum — more makes the engine run audibly loud. Avoid the low-RPM dead zone I call “Italian Highway syndrome” and start adjustments from 2000 RPM (safer above 2000).
This is the text summary. Paid attendees of our Q&A #1 (April 2026) got my live walkthrough — I demonstrated this on a real ECU binary in WinOLS, pointing to actual maps, scrolling DAMOS folders, showing byte-level changes. For the full diesel calibration methodology, see our Bosch EDC17 tuning guide →. Register free for our next Open Q&A → — live with me, agenda forming.
The question — from our Q&A #1
Marek asked during our first live Q&A:
“In this course you mention adjusting the injection timing advance. Can you explain how and in which maps it’s used, and how much it is typically increased? Also — if I want to adjust the start of injection maps, by how many degrees should I change them? By 10% or directly in degrees, like 2 degrees?”
Three questions in one. I’ll start with “degrees vs percent”, then walk through which specific maps in the EDC17 tree to edit and which to leave alone.
Why degrees, not percent
The SOI map is independent of fuel amount. Changing it has no influence on fuel — we only tell when the main injection should fire. So changing by percentage won’t give the exact efficiency math — degrees do (00:31:50).
Why percent doesn’t work for SOI
Most maps in an ECU represent a quantity — fuel mass, boost pressure, airflow. Percentage edits make sense because +10% of a quantity has a physical meaning.
SOI is different. It represents a timing event — “at what crankshaft angle does the main injection fire?” Without a baseline fuel amount to scale, percent gives no exact efficiency math — degrees do.
The 1° ≈ 1% efficiency rule
For piston engines like diesel:
+1 degree SOI advance ≈ +1% efficiency
+2 degrees SOI advance ≈ +2% efficiency
At +2 degrees that’s ~2% more torque and power at the same fuel — or equivalently, ~2% less consumption at the same load during polite driving (00:35:02).
Why not +3 or +5 degrees
Past +2 degrees, the engine runs audibly louder (00:34:00). That’s where I stop.
Ceiling: +2 degrees, no more.
The “Italian Highway syndrome” — the dead zone to avoid
I named this “syndrome of the Italian highway”. If the car stays for a long time, the engine is very warm, the intercooler is very warm, and then you rapidly start — if the boost comes, the fuel can start to burn in many points itself, without starting from the expected point of the combustion chamber. Avoid this (00:33:09).
Look at any factory SOI map on EDC17 — you’ll see a hole in the low-RPM area. This isn’t a calibration oversight. It’s a deliberate safety zone for this scenario:
- Car stays for a long time, engine very warm, intercooler very warm
- Driver rapidly opens throttle
- Boost comes up fast → fuel starts to auto-ignite in multiple combustion chamber points (not the expected SOI position)
The factory hole in the SOI map is the protection — don’t remove it. Don’t advance SOI in the Italian Highway region.
The 4-step SOI workflow
Step 1 — Start from 2000 RPM or above
My safe starting point: 2000 RPM, even safer >2000. The Italian Highway hole sits in the low-RPM area — start above it.
Step 2 — Also modify lower LOAD zones (not lower RPM)
Different axis. You want to improve efficiency at polite driving — moderate RPM, low-to-moderate load. This is where most daily driving happens, and where 1-2 degrees of SOI advance gives noticeable fuel economy improvement.
Step 3 — Correct non-linearity → linear
Physics rule:
- If the engine revs twice as fast, the ignition must fire twice as fast
- Fuel burns at a roughly constant speed (combustion chemistry-limited)
- Therefore: SOI timing should scale linearly with RPM
If the factory map shows non-linearity (curve, step, plateau) in the region you’re tuning → straighten it to linear. This matches the combustion-physics expectation above.
Step 4 — +1 to +2 degrees across the post-2000 zone
When I say “+1, +2”, I mean a range across the map — not a flat ceiling. Lower load/RPM gets +1, higher load/RPM gets +2, with linear interpolation between. A flat +2 across the whole post-2000 zone is more aggressive than what I’d recommend.
Which maps to edit — the EDC17 project tree
Now the practice — which maps to actually touch (00:36:11).
Default EDC17 map order (front to back):
| # | Map | DAMOS reference | Edit for SOI tuning? |
|---|---|---|---|
| 1 | Main injection position (values) | — |  Leave alone — not the timing map |
| 2 | Main injection limits | — | Leave alone |
| 3 | Pre-injection section (angles) | InjCrv_PiI1 adjacent |
Different system — pre-injection timing (KB-01 forthcoming this week) |
| 4 | Pre-injection maps (amount of fuel) | InjCrv_PiI1 / InjCrv_qPiI1Bas |
Different system — pre-injection quantity |
| 5 | Main injection timing (phases) | — | Don’t modify — these are used to divide main injection into phases |
| 6 | Main injection angle (phases) | InjCrv_MI1 / InjCrv_phiMI1Bas |
 THIS is the SOI map to edit |
| 7 | Post-injection values | adjacent | Different system from main SOI |
| 8 | Post-injection angles | adjacent | Negative angles (after TDC), leave alone |
Post-injection angles explained: they’re negative (e.g., -80° after TDC = in expansion stroke, just before the exhaust valve opens at ~130-150°). Completely different system from main SOI.
MD1 and some EDC17 variants — reversed order
On MD1 (and some EDC17 revisions), the order flips. My reference point: the torque limit structure. If the SOI maps are moved to the front, the order is reversed:
- Post-injection first
- Main injection
- Pre-injection last
Practical tip: if you can’t find the main injection angle after the torque limit in the default position, look backwards. In MD1 (or EDC17 variants where maps are moved to the front), the order is reversed: post → main → pre-injection (00:39:19).
Maps referenced in this guide
| Concept | DAMOS Folder | Map ID | ECU | Deep dive |
|---|---|---|---|---|
| Main injection SOI timing (the editable map) | InjCrv_MI1 |
InjCrv_phiMI1Bas |
EDC16, EDC17, MD1 | This KB (hub) |
| Pre-injection quantity (different system) | InjCrv_PiI1 |
InjCrv_qPiI1Bas |
EDC16, EDC17, MD1 | KB-01 — 4-tell identification (forthcoming this week) |
| Rail pressure (the other efficiency lever) | Rail_SetPoint |
Rail_pSetPointBas |
EDC16, EDC17, MD1 | KB-05 — +10% safe zones (forthcoming this week) |
Related on Tuners Guild
- Pre-injection = the holy grail of tuning: KB-02 Why 21% diesel math yields 10-15% real gain (forthcoming this week) — pre-injection is the #1 lever, SOI is complementary
- Synchronous monitoring pattern: KB-08 EDC17C46 driver wish no-start — SOI doesn’t trip monitoring but the concept of “respect paired maps” applies to every timing edit
- MED17 torque conversion (gasoline cousin): KB-11 MED17 torque conversion path — same “physical units, not percent” principle in the gasoline torque structure
- Full diesel SOI workflow: Chip Tuning Diesel — Practice course — includes MD1 variant identification and all 8 injection-related maps
- Bosch EDC17 pillar: EDC17 Tuning Guide
- Course pricing and bundles: See pricing →
Want the full SOI workflow?
These are core concepts I teach in the Chip Tuning Diesel Practice course — Italian Highway syndrome, degrees-not-percent rule, linearity principle. The full workflow shows you how to identify SOI maps across EDC17 variants, MD1, and older EDC16 — plus the paired limit maps that stop aggressive advance from bypassing safety logic.
See the Chip Tuning Diesel course →
Your turn
Running SOI advance on a different diesel ECU — EDC16, EDC17 variant, MD1, Delphi DCM6, Siemens SID? Share your case:
- ECU code + engine
- Degrees of SOI advance you ran (1°, 2°, other)
- Whether you kept the Italian Highway zone untouched
- Noise / combustion behavior before and after (did the engine get louder?)
Cross-ECU comparison is the fastest way to see which platforms handle the +2° ceiling cleanly and which clatter early.