Unsuccessful Control Unit Programming Session Or Sporadic Malfunction Of Systems (LI00.19-N-075749)
Reference number: LI00.19-N-075749
UNSUCCESSFUL CONTROL UNIT PROGRAMMING SESSION OR SPORADIC MALFUNCTION OF SYSTEMS
TECHNICAL SERVICE BULLETIN
| SPRINTER: | Sprinter 906 & 907; Metris 447 |
| FUNCTION GROUP: | 00.19 - Electrical Vehicle, complete network |
COMPLAINT
Various issues including control unit programming procedure will not complete successfully/no newer software found, communication faults, or sporadic malfunction of systems.
CAUSE
Aftermarket CAN device could be installed into the vehicle's CAN network. Such devices can be but are not limited to, remote start modules, CAN blockers, or high idle modules.
REMEDY
A successful control unit programming session cannot be ensured while aftermarket devices are connected to the vehicle's CAN network.
Some of the device companies supply a bypass to allow control unit programming.
To avoid an unsuccessful control unit programming session:
- During scheduling or checking-in the customer for an appointment, ask if any aftermarket devices such as remote start are installed
- Check the key ring for non-Mercedes-Benz remote or fob
- Inspect the vehicle's instrument panel for warning labels of such devices
- In case of remote start on 907, most will be connected between the CPC and EZS. The CPC is visible without panel removal. Most of the aftermarket harnesses will have multiple of the same color wire.
- In case of High idle device on 907, most will be installed near the SAM and F152.
Please perform control unit update of EZS. Each time the screen with the yellow box ("control unit does not respond") appears, press "Abort". It could come up multiple times (up to 20), but afterwards Control unit update of EZS will start.
The following AddOns have been released as of 1/11/2023 to remove error message when performing the update after the EZS has entered bootloader mode.
AddOn 25005 for XENTRY 09/2022
AddOn 24994 for XENTRY 12/2022
If the EZS is not recovered, please create an XSF ticket.
ATTACHMENTS
| File | Description |
|---|---|
| remote start warning label.png | example of remote start label |
| aftermarket CPC connector.png | example of aftermarket harness at CPC |
SYMPTOMS
| Overall vehicle > Networking > CAN/FlexRay communication > Malfunction |
| Overall vehicle > Networking > Gateway communication > Malfunction |
OPERATION NUMBERS/DAMAGE CODES
| Op. no. | Operation text | Time | Damage code | Note |