Sign in

View The Full Version : That the interface writes the ENTIRE eprom from the obd?



Nitro
26-09-2013, 17:28
Raga, I have a Focus 16c3 that hangs out with a lot of ease? when the map and every time I have to go to Ford and spend 70 euro.
The BDM, after a bad experience, I don't even want to hear appoint for a backup.
For? I have heard of people that resets the blocks from the obd.

So my question is ? the following: which interface ? able to read (and write) all the 3 files that are read in BDM directly from the obd? At that cost you can? get it?

In the alternative, that the cost to go from a guy that resets the errors?

ecuboost
27-09-2013, 17:44
but interfaces that read everything from the obd, maybe there are...to reset the errors that you want to say? remove the dtc?

passion engines
27-09-2013, 18:13
Hello Nitro, your edc16xxx ? scabby with tool ori, that I know there is a tool but it's only Siemens and marelli

Nitro
27-09-2013, 18:23
I do not intend to delete his fame but remove engine failure when I write.
The Ford and capable, from the serial to enter in all the parts of the control unit. I know why? I have adapted the ecu socket to collapse.
Then I know of people who claim to be able to reset the ecu in error without bdm. I read somewhere that using another protocol (and then the other interface)

msport (exil77grande)
28-09-2013, 01:17
Take a kess v2 and you are quiet.

Nitro
29-09-2013, 01:20
Maybe I explained it wrong. I mean errors in the compile the map that they can send in the recovery unit, not writing errors. The kess and capable of remedy to these?

Or once I have selected the ecu is wrong (they are not stupid. And a long story to explain) with mpps v5 and at the end of writing the ecu was working but the car was in recovery. I could restore with the kess?

Nitro
29-09-2013, 01:23
For recovery I mean malfunction indicator light engine turned on, written engine failure on the dashboard and the machine that works with limited performance. All non-resettable via obd (the error I can see it but you can't delete)

sno74
29-09-2013, 02:06
post the fault code and see why? do not remove if you do not cancel ? this then you don't need a toll, but understand what ? the failure.....

sportknight
29-09-2013, 03:22
sorry but do you want a generic diagnosis that will erase the error at this point...

autocom!!

ugoboss
29-09-2013, 09:12
Maybe I explained it wrong. I mean errors in the compile the map that they can send in the recovery unit, not writing errors. The kess and capable of remedy to these?

Or once I have selected the ecu is wrong (they are not stupid. And a long story to explain) with mpps v5 and at the end of writing the ecu was working but the car was in recovery. I could restore with the kess?

for me, you and nitro are you doing a bit of confusion, what you are looking for good or bad, almost all of the interfaces, the mpps has the writing of recovery, the kess (I do not know well) say that she has a recovery function really good, but it depends on the type of lock that has the ecu, many times you fail, even with the official diagnosis, then every case, and' if'.

faberecu
29-09-2013, 23:03
Is the diagnosis official Ford pu? reprogram your Ecu only ori or updates

As said above, sometimes nothing to do sometimes clones from 4 money work where ori fail happened to me, the bdm100 has revived an Ecu with bdm official has not been possible to write

Nitro
29-09-2013, 23:42
I repeat, that the errors of which I speak does not remain even with the diagnosis ford but only by reprogramming the ecu. To do that? I know two streets:bdm and diagnosis official via obd. I confirm that there are no other interfaces able to reprogram via obd?

Trust me, you are not paranoid! The focus (my ? 16c3) and very easy to send in error even for a professional, let alone a geek without a driver experience like me.
Before you start messing around I have to find a way to restore them

ugoboss
30-09-2013, 07:08
I don't like to repeat myself , but I do, you get a gallo2 with bdm and you're right, you make a backup and resume whenever you want, and the only way to be sure.

faberecu
01-10-2013, 15:00
quoto!
total read when still works!

ago27
04-10-2013, 06:52
I would like to join, now is the rooster clone and really at the top have made the version v53 going really well...

Nitro
08-10-2013, 17:48
Ok, to make? as you say.

Seen that ? finished with the talk of the bdm toglietem a curiosity? : my bdm 100 when I asked him to connect to my edc 16c3 made a noise type tics and then it returned the error that it was not able to connect. According to your experience ? the bdm is not working, the ecu is burnt or simply a problem of Inc ompatibilit? between the two?

ecutuningpro
08-10-2013, 18:09
or did you connect the strip to the contrary by burning out the unit. or simply you've done some connection evil.

ago27
08-10-2013, 18:43
The tic feel, and perfectly normal, and the rel? that is located within the bdm, for the error may be of all, you should explain what process you used to figure out where you were wrong.

ugoboss
08-10-2013, 19:14
Ok, to make? as you say.

Seen that ? finished with the talk of the bdm toglietem a curiosity? : my bdm 100 when I asked him to connect to my edc 16c3 made a noise type tics and then it returned the error that it was not able to connect. According to your experience ? the bdm is not working, the ecu is burnt or simply a problem of Inc ompatibilit? between the two?

what did you use to connect to the ecu, strip, or schedule in spring, feed the ecu from the comb I have through the bdm.

Nitro
08-10-2013, 20:44
I used strip welded on to the unit. Bdm powered by the network, and the control unit powered by bdm