Yhoni (23rd September, 2020)
Yhoni (23rd September, 2020)
Last edited by bobolin4o; 24th September, 2020 at 06:49 AM.
NO PASSWORDS FOR ANYONE, EXCEPT THE RECIPIENT OF THE FILE !!!
If your PM box is full, clean it right now...
Otherwise, your requested file will be deleted... for ever!
Hi bobolin4o, I'm not sure what steps to take to fix the problem.
1- write virgin file 24c04 to ECU
2 -Synchronize ECU with EWS3 with ISTA + program?
3 - Delete dtc?
Have I skipped a step?
Thank you.
If my post has helped you, do not forget to click on the "THANKS" and "REPUTATION" button !!!
I do not answer in private questions that can be solved in public.
You have to write virgin file, synchronize ECU with EWS and do adaptations (especially "Pump Characteristic Map"), which are in the list (in the screenshot).
You can do this things with ISTA+, old DIS, or Launch.
If you have ISTA+, use it with untouched eeprom in the ECU, make full test of the car, calculate test plan... ISTA will tell you what to do then.
Regards!
Last edited by bobolin4o; 25th September, 2020 at 06:30 AM.
NO PASSWORDS FOR ANYONE, EXCEPT THE RECIPIENT OF THE FILE !!!
If your PM box is full, clean it right now...
Otherwise, your requested file will be deleted... for ever!
Yhoni (25th September, 2020)
And? Where is the report...?
NO PASSWORDS FOR ANYONE, EXCEPT THE RECIPIENT OF THE FILE !!!
If your PM box is full, clean it right now...
Otherwise, your requested file will be deleted... for ever!
If my post has helped you, do not forget to click on the "THANKS" and "REPUTATION" button !!!
I do not answer in private questions that can be solved in public.
Hello,
Your problem might not be EEPROM fault!
This fault probably has nothing to do with EEPROM at all. This fault happens often when ECU adaptations are cleared with for example something like Delphi. BMW DIS or ISTA can be used to recalibrate the injection pump but this should not affect the starting of the car. I have seen many cars with this fault riding around (Even the M57 engine can get this fault code). This fault description and procedures to correct are given inside DIS aswell.
Since your car is VP44 then you probably have the common problem of VP44 internal ecu failure - injection control solenoid MOSFET fault. This does not usually cause any fault codes inside ECU aswell.
Incase of ISN not matching you should get a corresponding EWS fault in DDE aswell when you are starting the car.
In my opinion the eeprom fault code is a red herring in your case and a misdiagnosis of nonstarting issue but could also be yes a problem with EEPROM ofcourse.
VP44 ecu failure is a much more common issue than EEPROM corruption for M47.
In case Im right and you are going the route of alternative pump ECU then you should know automatic and manual car ECUs are different and NOT interchangeable.
In anycase report back.
Yhoni (30th September, 2020)
Hello bobolin4o, I have tried to start the car but I have come across the list of faults that can be seen in the attached image.
Now the fault of the eprom in the ECU has disappeared (42 DDE (eeprom o config)) but new ones have appeared like the fault of the CAN network.
The vehicle returns error when trying to match the EWS with the engine ECU, it can also be seen in the attached image.
Does anyone know what the reason could be?
Thank you very much
If my post has helped you, do not forget to click on the "THANKS" and "REPUTATION" button !!!
I do not answer in private questions that can be solved in public.
Hello bobolin4o, with your eeprom file virginized the eeprom error (error 42 DDE (eeprom or config)) disappeared after correcting the maps of the injection pump with the ista-d, thank you very much.
But the vehicle continues without starting and I find the problem that ista-d does not allow me to match the DDE and EWS giving an error that can be seen in the attached image.
I have compared the original ECU file and your virginized file and yours does not have the ISN code engraved.
When trying to match the DDE and the EWS the ISTA-D shows the error that can be seen in the photo and does not succeed.
I have compared the eeprom files with the "ISN" program (you can see the screenshot in the attached file) and I can see that the original ECU file shows the code "75 F5" just like the EWS eeprom but the virginized shows a error.
Could you check the virginized file for any errors? Should the ISN code already be in the virginized eeprom file?
Thank you very much.
If my post has helped you, do not forget to click on the "THANKS" and "REPUTATION" button !!!
I do not answer in private questions that can be solved in public.
If my post has helped you, do not forget to click on the "THANKS" and "REPUTATION" button !!!
I do not answer in private questions that can be solved in public.
Try letting the ISN on the original eeprom and delete only the bytes after them 3 occurrences till the B3 with FF's and try again, that way the ISN still be matched and maybe allow sync.
bobolin4o (27th October, 2020)
Yhoni (31st October, 2020)
Bookmarks