Description of this code is "synchronization of DTC memory cannot be ensured."

Anyone ever experience this???? It appears to be rather obscure....

__________________
Did you just pass my 740 at 200 kmh in a 300SD?????

1978 300SD 'Phil' - 1,315,853 Miles And Counting - 1, 317,885 as of 12/27/2012 - 1,333,000 as of 05/10/2013, 1,337,850 as of July 15, 2013, 1,339,000 as of August 13, 2013



100,000 miles since June 2005 Overhaul - Sold January 25th, 2014 After 1,344,246 Miles & 20 Years of Ownership

I don't know about that specific problem...

But in general and guessing as to what that might possibly mean (I could be way off!)...

When computers transfer data, there are ways to verify or "double check" that the data was sent or received without any errors. And if that happens, the data is then retransferred.

So the above could be saying the code reader you are using is not capable of 2 way communications and therefore can't *confirm* data transfers (including DTC's) are error free?

Or that new software was previously installed to the vehicle, but it was never verified to be correct?

Or there is some internal or vehicle computer to computer communication problem where the accuracy of communications can't be verified?

Sort of like with people, one person says; "My number is 123456".
The other person says; "123456?"
The first says; "Yes, that is correct!"

Your explanation seems plausible. There are no malfunctions on the car, just the presence of this odd code....

__________________
Did you just pass my 740 at 200 kmh in a 300SD?????

1978 300SD 'Phil' - 1,315,853 Miles And Counting - 1, 317,885 as of 12/27/2012 - 1,333,000 as of 05/10/2013, 1,337,850 as of July 15, 2013, 1,339,000 as of August 13, 2013



100,000 miles since June 2005 Overhaul - Sold January 25th, 2014 After 1,344,246 Miles & 20 Years of Ownership

What scan tool are you using to read this? My experience has taught me always fall back on the factory tool or equivalent when you get odd codes over OBDII.

Sometimes one module will record a fault when other modules have a fault. Does your tool check all the computers?

-J

__________________
1991 350SDL. 230,000 miles (new motor @ 150,000). Blown head gasket

Tesla Model 3. 205,000 miles. Been to 48 states!
Past: A fleet of VW TDIs.... including a V10,a Dieselgate Passat, and 2 ECOdiesels.
2014 Cadillac ELR
2013 Fiat 500E.

I have access to the factory tool, the Snap-On Vantage and Launch Diagun, all give the same data...

__________________
Did you just pass my 740 at 200 kmh in a 300SD?????

1978 300SD 'Phil' - 1,315,853 Miles And Counting - 1, 317,885 as of 12/27/2012 - 1,333,000 as of 05/10/2013, 1,337,850 as of July 15, 2013, 1,339,000 as of August 13, 2013



100,000 miles since June 2005 Overhaul - Sold January 25th, 2014 After 1,344,246 Miles & 20 Years of Ownership

Bump. Anyone else run into code 930E? Seems to be very little info on the interwebs for this one...

__________________
Dave
Boise, ID
Check out my website photos, documents, and movies!

Is the code persistent? I.e. you clear it, but it comes back later?

If not, I have seen a number of times where a newish MB has all kinds of obscure haywire codes set, but clearing them, they do not return. After discussing with the owner, they admit that their battery went dead a few months back and they had it replaced at the corner Joe's Service Station. Seems these newer MB's are pretty sensitive to voltage, and too low voltage causes the computers and sensors to lose their minds.

__________________
1998 E300 turbodiesel

America's Rights and Freedoms Are Not The Enemy!

We could use some car history.

I'm thinking the body computer and ECM both carry trouble codes and the lists won't sync up. The instrument cluster might be involved also.

Have a look for a CAN filter, this car might have had the dash "corrected" and the ECM / body module is trying to update the dash.

It's nothing to worry about.

When you scan the car you are reading the faults as stored in the central gateway. You can then also go into the individual modules and read faults, check actual values ect. If something doesn't jive with how the gateway stores and report faults you can get a code like that. As long as you have no symptoms, don't bother wasting time with it.

__________________

90 300TE 4-M
Turbo 103, T3/T04E 50 trim
T04B cover .60 AR
Stage 3 turbine .63 AR
A2W I/C, 40 LB/HR
MS2E, 60-2 Direct Coil Control
3" Exh, AEM W/B O2
Underdrive Alt. and P/S Pulleys,
Vented Rear Discs, .034 Booster.
3.07 diffs 1st Gear Start

90 300CE 104.980
Milled & ported head, 10.3:1 compression
197° intake cam w/20° advancer
Tuned CIS ECU
4° ignition advance
PCS TCM2000, built 722.6
600W networked suction fan
Sportline sway bars
V8 rear subframe, Quaife ATB 3.06 diff

In my case (W211), it comes back immediately. Like, erase / clear codes, cycle ignition, run Quick Test again, and this is the only code that comes back instantly.

The description concerns me slightly, "Synchronization of the DTC memory cannot be ensured"... which I hope does not mean, "there may be faults/errors occurring which are not being stored properly".