2007 335i won't start

dyezak · 05-09-2017, 11:43 AM

This is the thing that sparks my interest now: 0x2AB4 DME, internal error: RAM checksum

That's generally associated with MSD80 DME MOSFETS blowing. If you google this you can buy new MOSFETS for like $2 at an electronic supply store and solder them in (it's not that difficult).

ETA - Your car will never start if those MOSFETS are blown. You'll get no spark. It'll sound like it wants to start, but will never catch.

CantComplain · 05-11-2017, 09:08 PM

Quote:

Originally Posted by dyezak

This is the thing that sparks my interest now: 0x2AB4 DME, internal error: RAM checksum

That's generally associated with MSD80 DME MOSFETS blowing. If you google this you can buy new MOSFETS for like $2 at an electronic supply store and solder them in (it's not that difficult).

ETA - Your car will never start if those MOSFETS are blown. You'll get no spark. It'll sound like it wants to start, but will never catch.

I feel like all of those errors were written 37k miles ago and wouldn't still be relevant at this point. If they were, the car would never have run. I'd love to know why they're still in the car but it has been running for quite some time after they were thrown. I can otherwise communicate with the car (via INPA, etc). Do you still think that could be the cause?

I have a little more info from diagnostics that I'll throw in a new post below.

mj6234 · 05-11-2017, 09:16 PM

Betting on the DME being bad. Look at the codes listed on this repair service.

https://circuitboardmedics.com/bmw-s...epair-service/

You have 2ACC, definitely less common than 30BA and 30BB, but still a symptom of a failed DME.

I just got my MSD80 piece of shit replaced with a MSD81 from a wrecked car. Used this guy and he was beyond awesome and fast.

Used DME - $109 + his service fee.

https://www.facebook.com/BMWAdvancedProgramming/

JuniorB · 05-12-2017, 03:45 PM

It sounds looks like you have a different ecu and its not communicating. Your kms shouldn't be off that much if any. Your best bet is to have a dealer reprogram everything. Kinda making since now after going thru the whole nine, someone thought that they could just throw one in there, and it would run, or,someone did a motor swap.

JuniorB · 05-12-2017, 03:51 PM

Disregard, the 2nd page didn't load, I didn't read the car was running, there right it bent the ecu, hope you figure it out!

CantComplain · 05-12-2017, 10:19 PM

OK man I have so many questions. And an update about INPA data. I'll TRY to keep it short.

INPA on EKP:

E R R O R M E M O R Y R E P O R T
-------------------------------------
Date: 05/11/17 17:36:15
ECU: EKP360
JobStatus: OKAY
Variant: EKP360
-------------------------------------------------------------
RESULT: 1 errors in error memory !
-------------------------------------------------------------
52948 Externer Fehler: CAN-ID 0xAA (TORQUE_3) fehlt(e)
Warning: F_HFK doesn´t exist in result record 1 !
Warning: F_UW_ANZ doesn´t exist in result record 1 !
Warning: F_ART_ANZ doesn´t exist in result record 1 !
Errorcode: CE D4 28
================================================== ===========

The rail pressure is 210kPa when it's been off. Goes to ~2900 kPa when cranking. That seems like there's fuel. I can't trigger the lpfp via INPA--I get an error "ERROR_ECU_CONDITIONS_NOT_CORRECT_OR_REQUEST_SEQUE NCE_ERROR." Not sure if it's a problem with INPA or prg files or the EKP or what. I do also get occasional INPA script errors but I get this on other ECUs as well. OK, that's INPA and fuel.

I removed the DME and popped it open. I'm not the first one in there. There's a sticker with a name on it and it's been opened before. There's some white marshmallow/foam stuff underneath the top circuit board. WTF is that? It looks fresh and appears to be some insulation--totally not sure about this. But the MOSFETS do NOT appear to have been replaced previously. Not sure what anyone would have been doing here. SO the questions:

Can I test the MOSFETS to see if they're a problem? Simple continuity?
Can I tell if this is my original DME? It communicates with INPA and I can see my VIN. The date code is within 2 weeks of my production date. Is that enough or is there some other way to tell? If it's been replaced, how does it need to be coded and can I confirm it was done correctly?

The last thing is about the dates on the errors again. Yes, I had all of these codes at 151512km, but the car currently has 207715. I was ready to discount these codes entirely because it's been 35000 miles since they were thrown and they were all starting from the same date. I assumed there was a collision at that mileage and the car was repaired. I mean, the car wouldn't run with all of those, at least not 35k miles right? Some of the other errors relate to throttle valve, and that appears to be OK per INPA. So...does everyone think these are current? I get that the symptoms seem to overlap, but then there's the EKP code as well.

I can see why the indy gave up. Would love to get feedback with this data.

dyezak · 05-13-2017, 12:43 AM

Quote:

Originally Posted by CantComplain

OK man I have so many questions. And an update about INPA data. I'll TRY to keep it short.

INPA on EKP:

E R R O R M E M O R Y R E P O R T
-------------------------------------
Date: 05/11/17 17:36:15
ECU: EKP360
JobStatus: OKAY
Variant: EKP360
-------------------------------------------------------------
RESULT: 1 errors in error memory !
-------------------------------------------------------------
52948 Externer Fehler: CAN-ID 0xAA (TORQUE_3) fehlt(e)
Warning: F_HFK doesn´t exist in result record 1 !
Warning: F_UW_ANZ doesn´t exist in result record 1 !
Warning: F_ART_ANZ doesn´t exist in result record 1 !
Errorcode: CE D4 28
================================================== ===========

The rail pressure is 210kPa when it's been off. Goes to ~2900 kPa when cranking. That seems like there's fuel. I can't trigger the lpfp via INPA--I get an error "ERROR_ECU_CONDITIONS_NOT_CORRECT_OR_REQUEST_SEQUE NCE_ERROR." Not sure if it's a problem with INPA or prg files or the EKP or what. I do also get occasional INPA script errors but I get this on other ECUs as well. OK, that's INPA and fuel.

I removed the DME and popped it open. I'm not the first one in there. There's a sticker with a name on it and it's been opened before. There's some white marshmallow/foam stuff underneath the top circuit board. WTF is that? It looks fresh and appears to be some insulation--totally not sure about this. But the MOSFETS do NOT appear to have been replaced previously. Not sure what anyone would have been doing here. SO the questions:

Can I test the MOSFETS to see if they're a problem? Simple continuity?
Can I tell if this is my original DME? It communicates with INPA and I can see my VIN. The date code is within 2 weeks of my production date. Is that enough or is there some other way to tell? If it's been replaced, how does it need to be coded and can I confirm it was done correctly?

The last thing is about the dates on the errors again. Yes, I had all of these codes at 151512km, but the car currently has 207715. I was ready to discount these codes entirely because it's been 35000 miles since they were thrown and they were all starting from the same date. I assumed there was a collision at that mileage and the car was repaired. I mean, the car wouldn't run with all of those, at least not 35k miles right? Some of the other errors relate to throttle valve, and that appears to be OK per INPA. So...does everyone think these are current? I get that the symptoms seem to overlap, but then there's the EKP code as well.

I can see why the indy gave up. Would love to get feedback with this data.

Sounds like your fuel is right, and INPA is a bitch so it sounds good. Watch the vids above.

CantComplain · 05-13-2017, 11:03 AM

Quote:

Originally Posted by dyezak

Sounds like your fuel is right, and INPA is a bitch so it sounds good. Watch the vids above.

thanks for the links! I tested 1-6 and got the same results for all. Pin 1's were all 0, open circuit. Pine 2's were all 1, closed circuit. Pin 3's were all in the range of 645-652. I don't know what this is but it's not a short circuit and since they're all roughly identical I assume they're good. All of the other MOSFETS also appear to pass as well, though the readings on pin 3 are slightly different than for the injectors.

Is this sufficient to eliminate the DME, or at least the MOSFETS as a suspect? Since I don't know for certain if the DME was replaced in troubleshooting, do you know a way to confirm it is coded correctly for the car?

dyezak · 05-13-2017, 07:46 PM

Quote:

Originally Posted by CantComplain

thanks for the links! I tested 1-6 and got the same results for all. Pin 1's were all 0, open circuit. Pine 2's were all 1, closed circuit. Pin 3's were all in the range of 645-652. I don't know what this is but it's not a short circuit and since they're all roughly identical I assume they're good. All of the other MOSFETS also appear to pass as well, though the readings on pin 3 are slightly different than for the injectors.

Is this sufficient to eliminate the DME, or at least the MOSFETS as a suspect? Since I don't know for certain if the DME was replaced in troubleshooting, do you know a way to confirm it is coded correctly for the car?

I don't think you can verify that without special equipment...but I could be wrong.

CantComplain · 05-20-2017, 02:28 PM

a bit of an update: in INPA i can see a different VIN in the MSD80 User Information screen. If I hit F3 "Plant" I see yet ANOTHER VIN. Both are e90s from roughly the same production date. Not sure why the mismatch here, but since neither matches my car, and it's clear the DME has been removed and opened, I'm assuming I need to get it virginized and programmed. I read somewhere that this will cause the injectors to be disabled and that may explain why it sounded like it would run with starter fluid. Or maybe I'm just reading too much into it.

Anyway, I think that's the next step.

JuniorB · 05-21-2017, 10:10 AM

From what've everyone says, injectors will run without coding, just not efficiently. Was the car running prior to all this, then died? Theses cars need to communicate by ecu, cas and key fob that is linked to a designated vin, they cannot be different in anyway. This may be the first step. If all three are from a different car, it should still start until your vin is burned into the modules, if your seeing a different vin on the ecu, it may not be matched to the cas. To eliminate all this speculation, you may have to pull the ecu, cas, and fob, and sent it to a specialist that can confirm there communication between the three. This can also trigger the alarm since there may be a mismatch somewere. Unless you can backtrack the original diagnostic from the beginning, I would start here since you've done the previous.

JuniorB · 05-21-2017, 10:13 AM

Quote:

Originally Posted by CantComplain

a bit of an update: in INPA i can see a different VIN in the MSD80 User Information screen. If I hit F3 "Plant" I see yet ANOTHER VIN. Both are e90s from roughly the same production date. Not sure why the mismatch here, but since neither matches my car, and it's clear the DME has been removed and opened, I'm assuming I need to get it virginized and programmed. I read somewhere that this will cause the injectors to be disabled and that may explain why it sounded like it would run with starter fluid. Or maybe I'm just reading too much into it.

Anyway, I think that's the next step.

That's suspect , someone thought they could just plug an ecu in and it would start, it won't ever without your vin and communication from the cas, and fob.

dyezak · 05-22-2017, 07:51 AM

Quote:

Originally Posted by CantComplain

a bit of an update: in INPA i can see a different VIN in the MSD80 User Information screen. If I hit F3 "Plant" I see yet ANOTHER VIN. Both are e90s from roughly the same production date. Not sure why the mismatch here, but since neither matches my car, and it's clear the DME has been removed and opened, I'm assuming I need to get it virginized and programmed. I read somewhere that this will cause the injectors to be disabled and that may explain why it sounded like it would run with starter fluid. Or maybe I'm just reading too much into it.

Anyway, I think that's the next step.

Yes, if you see different VIN's in the DME that means that the individual who replaced the DME didn't do it correctly. The DME will need to be removed along with the CAS and you'll need to send them to someone to match your DME to your CAS (only part of which is the VIN coding). The other part is the security key coding. Without the security keys matching between your CAS + DME + Key you can't start your car as injectors are disabled as a security feature.

Another option is to buy a DME + CAS + Key combo from a wrecked car (found on ebay).

JuniorB · 05-23-2017, 11:53 AM

Ya,that may be the best way to go,them you can have your vin reprogrammed. Having everything to match would be a first step if your communication is off,or pull your modules and have BMW match it up.

CantComplain · 06-12-2017, 12:33 PM

Hi Everyone, OP here. I hate it when I run across a thread with a similar issue and there's no resolution, so I'll update this with current status even though it's frustratingly not a complete resolution.

The car is now running, though relatively poorly from a mechanical perspective. Different issue. I took it to a local coder ad he was able to figure some stuff out and program the new-to-the-car ECU. The car has clearly been worked on in recent times, and probably by hack mechanics. So the #1 issue that needed to be overcome before anything else was programming the DME to the car. That's a no brainer, but it took me to post 32 to come to that realization. Input here drove me to INPA and that made that clear.

Car now runs but has ABS, BRAKE, SES and airbag lights on. DSC can't be communicated with, so I'm hoping that's an easy fix. I'll start a new thread on that because I can't find a good tutorial on diagnosing the DSC but don;t want to muck this thread up any more.

Thanks all for the help!

335e92tx · 06-12-2017, 09:18 PM

Quote:

Originally Posted by CantComplain

Hi Everyone, OP here. I hate it when I run across a thread with a similar issue and there's no resolution, so I'll update this with current status even though it's frustratingly not a complete resolution.

The car is now running, though relatively poorly from a mechanical perspective. Different issue. I took it to a local coder ad he was able to figure some stuff out and program the new-to-the-car ECU. The car has clearly been worked on in recent times, and probably by hack mechanics. So the #1 issue that needed to be overcome before anything else was programming the DME to the car. That's a no brainer, but it took me to post 32 to come to that realization. Input here drove me to INPA and that made that clear.

Car now runs but has ABS, BRAKE, SES and airbag lights on. DSC can't be communicated with, so I'm hoping that's an easy fix. I'll start a new thread on that because I can't find a good tutorial on diagnosing the DSC but don;t want to muck this thread up any more.

Thanks all for the help!

Good deal on operation . I imagine the ABS, brake and DSC are related. Start with getting the codes for your brakes.

musa · 06-15-2017, 02:23 PM

Quote:

Originally Posted by CantComplain

Hi Everyone, OP here. I hate it when I run across a thread with a similar issue and there's no resolution, so I'll update this with current status even though it's frustratingly not a complete resolution.
<snip>

Thanks for the update! I too came across multiple threads with the issue I was having but those threads were never concluded with a fix or otherwise. After I fixed my issue, I made it a point to update all my different forum posts with the resolution.

All the best with your new issue.

Scottycs · 02-18-2022, 08:53 PM

Did you discover your DSC communication error?

Quote:

Originally Posted by CantComplain

Hi Everyone, OP here. I hate it when I run across a thread with a similar issue and there's no resolution, so I'll update this with current status even though it's frustratingly not a complete resolution.

The car is now running, though relatively poorly from a mechanical perspective. Different issue. I took it to a local coder ad he was able to figure some stuff out and program the new-to-the-car ECU. The car has clearly been worked on in recent times, and probably by hack mechanics. So the #1 issue that needed to be overcome before anything else was programming the DME to the car. That's a no brainer, but it took me to post 32 to come to that realization. Input here drove me to INPA and that made that clear.

Car now runs but has ABS, BRAKE, SES and airbag lights on. DSC can't be communicated with, so I'm hoping that's an easy fix. I'll start a new thread on that because I can't find a good tutorial on diagnosing the DSC but don;t want to muck this thread up any more.

Thanks all for the help!

05-09-2017, 11:43 AM	#23
dyezak General of the Armies 160 Rep 661 Posts Drives: X5M Join Date: May 2011 Location: Plano, TX iTrader: (2)	This is the thing that sparks my interest now: 0x2AB4 DME, internal error: RAM checksum That's generally associated with MSD80 DME MOSFETS blowing. If you google this you can buy new MOSFETS for like $2 at an electronic supply store and solder them in (it's not that difficult). ETA - Your car will never start if those MOSFETS are blown. You'll get no spark. It'll sound like it wants to start, but will never catch.
	Appreciate 0 Quote

05-11-2017, 09:16 PM	#25
mj6234 Private First Class 34 Rep 108 Posts Drives: E92 335i Join Date: Nov 2011 Location: US iTrader: (0)	Betting on the DME being bad. Look at the codes listed on this repair service. https://circuitboardmedics.com/bmw-s...epair-service/ You have 2ACC, definitely less common than 30BA and 30BB, but still a symptom of a failed DME. I just got my MSD80 piece of shit replaced with a MSD81 from a wrecked car. Used this guy and he was beyond awesome and fast. Used DME - $109 + his service fee. https://www.facebook.com/BMWAdvancedProgramming/
	Appreciate 0 Quote

05-12-2017, 03:45 PM	#26
JuniorB Major 186 Rep 1,017 Posts Drives: 07 e60 525 N54 Join Date: Mar 2016 Location: Rhode Island iTrader: (0)	It sounds looks like you have a different ecu and its not communicating. Your kms shouldn't be off that much if any. Your best bet is to have a dealer reprogram everything. Kinda making since now after going thru the whole nine, someone thought that they could just throw one in there, and it would run, or,someone did a motor swap.
	Appreciate 0 Quote

05-12-2017, 03:51 PM	#27
JuniorB Major 186 Rep 1,017 Posts Drives: 07 e60 525 N54 Join Date: Mar 2016 Location: Rhode Island iTrader: (0)	Disregard, the 2nd page didn't load, I didn't read the car was running, there right it bent the ecu, hope you figure it out!
	Appreciate 0 Quote

05-12-2017, 10:19 PM	#28
CantComplain Second Lieutenant 118 Rep 220 Posts Drives: '17 6MT AW M2 Join Date: Aug 2016 Location: San Rafael, CA iTrader: (0)	OK man I have so many questions. And an update about INPA data. I'll TRY to keep it short. INPA on EKP: E R R O R M E M O R Y R E P O R T ------------------------------------- Date: 05/11/17 17:36:15 ECU: EKP360 JobStatus: OKAY Variant: EKP360 ------------------------------------------------------------- RESULT: 1 errors in error memory ! ------------------------------------------------------------- 52948 Externer Fehler: CAN-ID 0xAA (TORQUE_3) fehlt(e) Warning: F_HFK doesn´t exist in result record 1 ! Warning: F_UW_ANZ doesn´t exist in result record 1 ! Warning: F_ART_ANZ doesn´t exist in result record 1 ! Errorcode: CE D4 28 ================================================== =========== The rail pressure is 210kPa when it's been off. Goes to ~2900 kPa when cranking. That seems like there's fuel. I can't trigger the lpfp via INPA--I get an error "ERROR_ECU_CONDITIONS_NOT_CORRECT_OR_REQUEST_SEQUE NCE_ERROR." Not sure if it's a problem with INPA or prg files or the EKP or what. I do also get occasional INPA script errors but I get this on other ECUs as well. OK, that's INPA and fuel. I removed the DME and popped it open. I'm not the first one in there. There's a sticker with a name on it and it's been opened before. There's some white marshmallow/foam stuff underneath the top circuit board. WTF is that? It looks fresh and appears to be some insulation--totally not sure about this. But the MOSFETS do NOT appear to have been replaced previously. Not sure what anyone would have been doing here. SO the questions: Can I test the MOSFETS to see if they're a problem? Simple continuity? Can I tell if this is my original DME? It communicates with INPA and I can see my VIN. The date code is within 2 weeks of my production date. Is that enough or is there some other way to tell? If it's been replaced, how does it need to be coded and can I confirm it was done correctly? The last thing is about the dates on the errors again. Yes, I had all of these codes at 151512km, but the car currently has 207715. I was ready to discount these codes entirely because it's been 35000 miles since they were thrown and they were all starting from the same date. I assumed there was a collision at that mileage and the car was repaired. I mean, the car wouldn't run with all of those, at least not 35k miles right? Some of the other errors relate to throttle valve, and that appears to be OK per INPA. So...does everyone think these are current? I get that the symptoms seem to overlap, but then there's the EKP code as well. I can see why the indy gave up. Would love to get feedback with this data.
	Appreciate 0 Quote

05-20-2017, 02:28 PM	#32
CantComplain Second Lieutenant 118 Rep 220 Posts Drives: '17 6MT AW M2 Join Date: Aug 2016 Location: San Rafael, CA iTrader: (0)	a bit of an update: in INPA i can see a different VIN in the MSD80 User Information screen. If I hit F3 "Plant" I see yet ANOTHER VIN. Both are e90s from roughly the same production date. Not sure why the mismatch here, but since neither matches my car, and it's clear the DME has been removed and opened, I'm assuming I need to get it virginized and programmed. I read somewhere that this will cause the injectors to be disabled and that may explain why it sounded like it would run with starter fluid. Or maybe I'm just reading too much into it. Anyway, I think that's the next step.
	Appreciate 0 Quote

05-21-2017, 10:10 AM	#33
JuniorB Major 186 Rep 1,017 Posts Drives: 07 e60 525 N54 Join Date: Mar 2016 Location: Rhode Island iTrader: (0)	From what've everyone says, injectors will run without coding, just not efficiently. Was the car running prior to all this, then died? Theses cars need to communicate by ecu, cas and key fob that is linked to a designated vin, they cannot be different in anyway. This may be the first step. If all three are from a different car, it should still start until your vin is burned into the modules, if your seeing a different vin on the ecu, it may not be matched to the cas. To eliminate all this speculation, you may have to pull the ecu, cas, and fob, and sent it to a specialist that can confirm there communication between the three. This can also trigger the alarm since there may be a mismatch somewere. Unless you can backtrack the original diagnostic from the beginning, I would start here since you've done the previous.
	Appreciate 0 Quote

05-23-2017, 11:53 AM	#36
JuniorB Major 186 Rep 1,017 Posts Drives: 07 e60 525 N54 Join Date: Mar 2016 Location: Rhode Island iTrader: (0)	Ya,that may be the best way to go,them you can have your vin reprogrammed. Having everything to match would be a first step if your communication is off,or pull your modules and have BMW match it up.
	Appreciate 0 Quote

06-12-2017, 12:33 PM	#37
CantComplain Second Lieutenant 118 Rep 220 Posts Drives: '17 6MT AW M2 Join Date: Aug 2016 Location: San Rafael, CA iTrader: (0)	Wrap up Hi Everyone, OP here. I hate it when I run across a thread with a similar issue and there's no resolution, so I'll update this with current status even though it's frustratingly not a complete resolution. The car is now running, though relatively poorly from a mechanical perspective. Different issue. I took it to a local coder ad he was able to figure some stuff out and program the new-to-the-car ECU. The car has clearly been worked on in recent times, and probably by hack mechanics. So the #1 issue that needed to be overcome before anything else was programming the DME to the car. That's a no brainer, but it took me to post 32 to come to that realization. Input here drove me to INPA and that made that clear. Car now runs but has ABS, BRAKE, SES and airbag lights on. DSC can't be communicated with, so I'm hoping that's an easy fix. I'll start a new thread on that because I can't find a good tutorial on diagnosing the DSC but don;t want to muck this thread up any more. Thanks all for the help!
	Appreciate 0 Quote