KESS3 3.51 MDG1 Bench Update: What Workshops Must Verify
Prepared and checked: 7 September 2026
Release boundary: A planning summary of Alientech KESS3 Upgrade 3.51 for selected Bosch MDG1 control units. It is not an unlocking tutorial, a wiring reference, a vehicle-level compatibility guarantee or evidence of support in KT200II or any other tool.
Source note: Prepared by the ECU Tool Store editorial team from Alientech’s public release page, KESS3 product page and product-update index. ECU Tool Store did not test this release and is not affiliated with Alientech.
What changed: On 3 September 2026, Alientech announced new KESS3 Bench protocols for a defined set of Bosch MDG1 ECUs described by the manufacturer as “Locked.” The new route applies after an initial provider-documented BOOT unlock performed with the KESS3 Unlock Module. Alientech says the protocols require CAR BENCH/BOOT activation and an active subscription. That is a staged, tool-specific workflow—not permission to assume every MDG1, every software revision or every vehicle carrying a familiar model name is covered.
The release facts, without the marketing shorthand
| Item | Alientech release information | Workshop meaning |
|---|---|---|
| Release | KESS3 Upgrade 3.51, dated 3 September 2026 | Check that the installed suite and account expose the current protocol before booking |
| Connection route | Bench after the required initial BOOT unlock | Bench availability is conditional; it is not the first access step for an untouched protected ECU |
| Named ECU families | MD1CS003, MD1CS069, MD1CP007, MD1CS012, MG1CS042, MD1CS004 HW80, MG1CS031, MD1CP006, MD1CS005 and MG1CS002 | Match the exact ECU identification and hardware variant, not only the vehicle |
| Commercial prerequisites | CAR BENCH/BOOT activation, active subscription and KESS3 Unlock Module for the initial BOOT procedure | Hardware ownership alone does not establish access |
| Application period | Applications from 2021 onward are listed in the release | A model year is only a filter; it does not replace ECU identification |
The release also lists a broad group of passenger-car, light-commercial, heavy-duty and tractor applications. A long vehicle list is useful for finding possible jobs, but it should not be copied into a work order as a blanket promise. Vehicles sharing a name or production year can carry different engines, ECU hardware, software states and prior service histories. The current protocol entry and its manual remain the operational source for the individual job.
Why “Bench after unlock” is a two-stage condition
Alientech’s announcement separates the initial access event from later Bench work. The manufacturer says an applicable protected ECU is first handled through its KESS3 Unlock Module and BOOT unlock procedure; after that step, subsequent work can use the connector in Bench without reopening the unit. This article intentionally does not reproduce the procedure, patch instructions, connections or access details. Those belong only to the current manufacturer documentation available to an authorized user for the exact protocol.
For scheduling, the distinction matters. A workshop should not quote a routine Bench appointment for a unit whose initial state is unknown. Ask whether the ECU is original, previously opened, replaced, cloned, updated by a dealer or handled by another programming service. None of those answers proves eligibility, but they identify uncertainty that must be resolved before the vehicle occupies a bay.
The release’s efficiency claim should also be read narrowly. Avoiding another opening after a successful initial workflow may reduce repeated physical access for later supported operations. It does not guarantee a faster first job, a successful write, recovery from an earlier interruption or suitability of a calibration file. Stable power, a verified original backup, the correct protocol and a lawful repair purpose remain separate decisions.
A safer intake check before accepting the job
Use the following questions to decide whether the request is ready for protocol confirmation. They do not replace the KESS3 manual.
- Identify the control unit. Request clear photos of the complete ECU label and connectors, plus the vehicle VIN through a private support channel. Match the Bosch family, hardware reference and application; do not infer MD1CS004 HW80 from a similar housing.
- Confirm the current state. Record whether the ECU has been opened, unlocked, updated, replaced or previously programmed. If the customer does not know, mark the state unknown rather than guessing.
- Verify the account prerequisites. The technician should confirm the required CAR BENCH/BOOT activation, active subscription and access to the correct KESS3 Unlock Module. A screenshot of the current authorized protocol entry is more useful than a generic product advertisement.
- Read the current protocol instructions. Check the exact mode, accessories, cautions and supported functions shown in Alientech Suite for that ECU. Stop if the entry is absent or does not match the hardware.
- Define the lawful service goal. Record whether the job is diagnosis, repair, replacement or a permitted calibration service. Decline requests involving emissions defeat, odometer manipulation, immobilizer bypass, stolen-module access or other unauthorized changes.
- Plan evidence and recovery boundaries. Agree on stable power, file naming, original backup retention, customer authorization and the point at which the technician will stop and contact Alientech support.
This intake record helps customer service answer the useful question—“Is this exact job ready to verify?”—instead of the unanswerable question—“Does it do all locked MDG1?”
What the announcement does not establish
Upgrade 3.51 does not establish universal MDG1 coverage, nor does a vehicle appearing in the release prove that every engine and ECU revision is supported. It does not say that the initial protection step can be skipped. It does not transfer support to KT200II, KESS V2, Flex, FoxFlash or another programmer. Protocol names and accessories are vendor-specific; a matching ECU family in another tool must be verified independently in that provider’s current documentation.
The announcement also should not be used as a file-quality endorsement. Read/write access and a completed checksum process do not prove that a requested calibration is lawful, technically appropriate or safe for the vehicle. Workshops remain responsible for vehicle identification, authorization, file provenance, electrical conditions and post-service validation.
Stop before connecting when the ECU identification is incomplete, the listed hardware suffix does not match, the required activation or subscription is unavailable, the initial unlock state cannot be established, the protocol manual is inaccessible, or the requested work would bypass legal or security controls. Send Alientech support the protocol search result, ECU label photos, KESS3 serial/account context, software version, operation history and exact message—without sharing customer secrets publicly.
Four practical questions
Can a workshop now use Bench first on every listed MDG1?
No. Alientech describes the new Bench access as available after its required initial BOOT unlock workflow. Confirm the exact protocol and current ECU state in the authorized software before planning the connection mode.
Does “from 2021” mean every 2021-or-newer listed vehicle is supported?
No. It describes the application range in the release, not a vehicle-wide guarantee. Exact ECU family, hardware, software and protocol availability must match.
Does this release prove KT200II supports the same ECUs?
No. It is an Alientech KESS3 release. Support in KT200II or another programmer requires separate current evidence from that tool’s provider for the exact ECU and mode.
Can a previously unlocked ECU automatically use the new Bench protocol?
Do not assume so. Record who performed the earlier work and verify the ECU’s current state, exact hardware and software identifiers, KESS3 account prerequisites and live protocol instructions. An undocumented prior unlock is a reason to pause, not proof of eligibility.
Commercial disclosure: ECU Tool Store sells ECU programming products and may benefit from related purchases. This independent editorial summary reports a third-party manufacturer update; it is not an Alientech sales page, affiliation claim or ECUToolStore test.
For broader planning, compare the difference between ECU flashing and remapping and review the ECU programmer selection checklist. Confirm KESS3-specific eligibility only through Alientech’s current Suite, protocol manual and support channel.