Customer bring me 2007 bmw 335i, customer complaint he can not pass emissions testing here in US because when they plug in to check readiness monitors, their scanner can not communicate.

I plug in AHII, communication is fine, I find out that he had previous shop install msd81 dme in place of faulty msd80. They perform isn change however the dme still show the donor VIN. I reprogrammed the dme and now the chassis VIN match the dme VIN however still no communication using global obd2 scanner and can not read emissions readiness monitor. I forsure thought this was because the VIN mismatch however that does not seem to be the case.

Has anyone seen this issue before, I dont know what to tell my customer. I assume the obd2 port has power and ground and communication as I was able to connect and perform programming with AHII. Does global obd2 use different protocol and maybe that communication line is down?

---

Customer bring me 2007 bmw 335i, customer complaint he can not pass emissions testing here in US because when they plug in to check readiness monitors, their scanner can not communicate.

I plug in AHII, communication is fine, I find out that he had previous shop install msd81 dme in place of faulty msd80. They perform isn change however the dme still show the donor VIN. I reprogrammed the dme and now the chassis VIN match the dme VIN however still no communication using global obd2 scanner and can not read emissions readiness monitor. I forsure thought this was because the VIN mismatch however that does not seem to be the case.

Has anyone seen this issue before, I dont know what to tell my customer. I assume the obd2 port has power and ground and communication as I was able to connect and perform programming with AHII. Does global obd2 use different protocol and maybe that communication line is down?

Did you check the connectors that plug into DME? Because they are known to have corrosion on various pins causing this issue of no communication. Or sometimes a broken pin. I just did one that had half a pin broken and corrosion.

I can fix it,
PM me

So the early 2007 model 3 series uses a different protocol via the dlc to check emissions readiness / generic obd2 mode. He has a msd81 out of a 2010 3 series currently installed and it runs and drives the vehicle just fine..however 2010 3 series uses a different protocol and different wires on the dlc. I doubt this is a matter of switching pins on the dlc as my assumption is no matter what customer does he will need another msd80 in order to talk to generic mode enabling him to take it in for emissions.

Anyone have any work arounds for this?

---

Customer bring me 2007 bmw 335i, customer complaint he can not pass emissions testing here in US because when they plug in to check readiness monitors, their scanner can not communicate.

I plug in AHII, communication is fine, I find out that he had previous shop install msd81 dme in place of faulty msd80. They perform isn change however the dme still show the donor VIN. I reprogrammed the dme and now the chassis VIN match the dme VIN however still no communication using global obd2 scanner and can not read emissions readiness monitor. I forsure thought this was because the VIN mismatch however that does not seem to be the case.

Has anyone seen this issue before, I dont know what to tell my customer. I assume the obd2 port has power and ground and communication as I was able to connect and perform programming with AHII. Does global obd2 use different protocol and maybe that communication line is down?

Did you check the connectors that plug into DME? Because they are known to have corrosion on various pins causing this issue of no communication. Or sometimes a broken pin. I just did one that had half a pin broken and corrosion.

Yes I inspected the dme and pins, all look good.

---

Hello did you ever figure out this problem?
I' am dealing with the same situation

Unfortunately no, I did not see customer again. As far as I know, he was planning to send dme to bimecu (levanime) but I dont know if he did or not. Levan claims to have a fix however will not share further information. Business is business so I understand.

---

Ok thank you!
I'll post a fix if I find one

That would be great, thank you

---

There are multiple copies of VIN stored on DME, programming with UIF enabled should change VIN in additional places. Otherwise this could be a UIF problem where records still exist of original vin, particularly in original UIF.

Thank you RocketSurgeon for that information. How do I change the setting to enable programming with UIF if you don't mind me asking..?

---

Maybe JB4 installed ? JB4 is piggyback module and common for N54 cars. It is blocking dme communication when it is active.

check communications for obd socket pin 9 and DME pin 21.regards

Anyone figure out fix? I’m having same issue..wonder what solution is so I can solve it in the future.

Anyone figure out fix? I’m having same issue..wonder what solution is so I can solve it in the future.

I have solution. PM me.

---

No PM is allowed. if you have the solution post it here!

I'm sorry, let me clarify. I do not give out solution / directions over PM. I only provide my paid services to repair the problem.

If this is not allowed, I will not do it anymore.

---