PDA

View Full Version : Phedra 2.2jtd edc16cp39 not found with edc16cp39 protocol, read as 1.6hdi edc16c34



teoturo
19th September, 2013, 07:11 PM
Dear Sirs,
900kms far from me I cooperate with a south-italy garage, they use a simple MPPS v12 and had today a Lancia Phedra for remapping.

Car has edc16cp39 ecu (see photo)

220296

MPPS has no edc16cp39 protocol for Lancia Phedra/Fiat Ulysse/Citroen and Peugeot identical models, so he tried to read with Fiat edc16cp39 protocol. "Ecu not found" was the result.

Mechanic tried to read ecu with edc16c34 Peugeot 1.6hdi protocol, and ecu was read with attached file.

Question is: will MPPS be able to write the ecu with the same protocol? I ask this because it's strange that 2.2jtd engine with edc16cp39 can be read with edc16c34 protocol for 1.6hdi engines, so I'm not sure if interface will be able to write and to calculate checksum.

In addition, is DPFoff ok in your opinion? I never worked on these 2.2 engines.

220295

ominimicu
19th September, 2013, 07:24 PM
DPf looks ok, may work, but i would NOT use MPPS on that ecu....too few cehcksum blocks..it may brick ecu.

teoturo
19th September, 2013, 07:37 PM
Have an idea of the reason why edc16cp39 protocol doesn't work and edc16c34 protocol (wrong) works?

What if MPPS writes a file with checksum already ok? In case, could you correct checksum?

ominimicu
19th September, 2013, 07:40 PM
checksum on mod files is not corrected, which makes me think its ecusafe solution for DPF off. strange you read via edc16c34..but MPPS is that wierd. problem is that he doesnt correct checksum as edc16c34...
i dunno i wouldnt write it unless you had a BDM just in case!

oem
19th September, 2013, 07:40 PM
Don't use MPPS for this ecu! If you have not another OBD tool use BDM.