DDE diesel control
Primary focus is diesel ECU read/write workflows, beginning with E-series DDE families already covered in development.
KS Flasher licenses
Access follows the vehicle, not a random file.
KS Flasher licenses unlock staged actions for supported BMW platforms. The account can sign in anywhere, but flashing access becomes tied to the identified vehicle, original stock backup, and server-side state.
Account based
VIN aware
Stock backup first
E-series rollout
Core tier
KS Flasher Access
Identify, connection state, first read, stock backup, and reviewed Stage 1 / Stage 2 tune delivery for supported vehicles.
Manual activation Full tierKS Flasher Full Access
Everything in Access, plus custom file selection, deeper write workflows, recovery-aware support, and engineer-reviewed cases.
Manual activationWhat the license controls
Only the right action appears at the right time.
Before login, only account, settings, and support make sense. Before identify, only connect and identify are active. After identify, first read appears. After the stock backup exists, normal read/write actions can be unlocked by license and vehicle state.
01Connect / Identify
02First Read
03Stage 1 / Stage 2 / Custom
04Write Tune / Recovery
Supported vehicles
BMW E-series first. More coverage as validation grows.
The list below is intentionally practical: model family first, then common diesel variants. Final support still depends on ECU family, software, read mode, and vehicle condition.
E60 / E61
520d, 525d, 530d, 535d. Main rollout family for M57 / M57N / M57N2 diesel workflows.
E90 / E91 / E92 / E93
318d, 320d, 325d, 330d, 335d where ECU family and read/write path match supported profiles.
E81 / E82 / E87 / E88
116d, 118d, 120d, 123d planned for staged support after validation.
E70 / E71
X5 and X6 diesel variants planned for staged support with additional checks.
Transmission support
Transmission features will be exposed only when the connected vehicle and license state make them relevant.
Stage and custom delivery
Stage files and custom .bin selection are handled as workflow choices, not as loose downloads without vehicle context.