Mercedes XENTRY / DAS: Installation, Star Diagnostic Setup, and Key Programming Limits
Mercedes diagnostics run on XENTRY (current) or DAS (older) through a Star Diagnostic multiplexer (C4 / C5 / C6). Key programming is handled server-side by Mercedes through TRP / XSF tickets, and pass-thru key programming isn't supported.
Mercedes-Benz diagnostics and programming run on XENTRY (the current application) or DAS (older, still used on some earlier models), communicating with the vehicle through a Star Diagnostic multiplexer. Setting Mercedes up is an Installation & Setup task, but the part that trips most shops up is that Mercedes key programming is handled server-side by Mercedes through a ticket system - not on the vehicle like most OEMs - and pass-thru key programming isn't supported at all. This guide covers the Mercedes software stack, the install prerequisites, how the key-ticket process works, the pass-thru limits, and XENTRY troubleshooting. For the specific question of whether a Mercedes key can be programmed with the OEM tool, see the linked XENTRY key article.
The Mercedes software and hardware stack
- XENTRY — the current Mercedes diagnostic and programming application. - DAS — the older diagnostic application, still used for some earlier models.
- Vediamo — engineering-level Mercedes software for advanced coding.
- Star Diagnostic multiplexer (C4 / C5 / C6) — the hardware interface between the laptop and the vehicle. It's also referred to as MB SD Connect in some channels.
Prerequisites
- Windows 11 Pro (XENTRY is sensitive to OS and .NET versions).
- 16 GB RAM.
- A Star Diagnostic multiplexer (C4, C5, or C6).
- An active Mercedes subscription (held on your own Mercedes account, separate from AE Tools).
- TRP credentials for key and programming work.
AE Tools can handle the Mercedes install as a paid setup service — contact AE Tools for scope and current pricing.
Mercedes key programming - server-side through TRP / XSF tickets
Mercedes keys are not programmed on the vehicle the way most OEMs do it. The order is released by Mercedes on their server through a ticket workflow:
1. Open a TRP (Technical Release Procedure) ticket through Mercedes.
2. Submit the required vehicle and customer documentation.
3. Register the vehicle as "present" in XENTRY Diagnosis (the vehicle registration step for key ordering).
4. Submit an XSF ticket to release the order.
5. Mercedes processes the request server-side.
6. Insert the new key and test.
For an all-keys-lost (AKL) situation, Mercedes processes it on their server — the prior keys are erased server-side, so there's no vehicle-side "release" step. Mercedes provides the programming release, and you use your key-entry programmer to insert and test the new key.
Pass-thru programming is not supported on Mercedes
AE Tools does not support Mercedes pass-thru programming, and for key work there generally isn't a viable third-party path:
- Pass-thru key programming through an AEZ Flasher 3 (for example on a 2009 R350) is not supported.
- For 2018–2020 Mercedes, no third-party key-programming tools exist — only factory software works.
- On newer Mercedes, XENTRY is the only sanctioned path.
If a customer asks about Mercedes pass-thru or aftermarket key programming on these vehicles, the answer is that it isn't supported — the work has to go through XENTRY (factory software) or a dealer.
Getting Mercedes credentials for a third-party tool
If you're using a third-party tool (such as an Autel) and need Mercedes credentials to authenticate against the security gateway:
1. Submit a support ticket through the AE Solutions support ticket system (this request is handled online, not by phone).
2. Specify the vehicle (for example, "2022 Mercedes"), the tool you're using, and the credential or security link you need.
3. Tech support processes the credential / technician-profile request.
Troubleshooting: XENTRY
"No-crank / no-start, drive authorization shows start-enabled, and the electronic steering lock shows 'no.'" This usually points to a VIN or module mismatch — often after a transmission or module swap. Re-verify the VIN and recheck the module configuration.
"VIN write fails." Usually the wrong calibration or the wrong gateway part number was selected — confirm both against the actual vehicle.
"XENTRY doesn't detect the multiplexer." A driver issue — reinstall the Star Diagnostic multiplexer drivers and reconnect.
For complex programming scenarios, AE Tools can work through XENTRY with you remotely.
Related articles
- Can I program a Mercedes key with the OEM tool (XENTRY)? - https://knowledgebase.aetools.us/can-i-program-a-mercedes-key-with-the-oem-tool
- VW / Audi ODIS Full Setup - GRP Login, TOTP, J2534 / VAS 6154 Setup, and Flat-Rate Subscription - https://knowledgebase.aetools.us/vw-/-audi-odis-full-setup-grp-login-totp-j2534-/-vas-6154-setup-and-flat-rate-subscription