Help on technical concepts

Reading the various discussions I'm trying to understand some of the technical concepts, and would like to ask you some questions to understand if they are on the right track.

- Reading and writing in the Obd would be equal to the serial reading ?
Through the reading in the serial/Obd not possible to do a full backup of the ECU ?
- To make a full backup of the ECU what should I save ?
- Reading and writing in the Bdm allows you to do a full backup of the ECU ?
- To connect Bdm you need to remove and open the ECU ?
- What does it mean to connect on Boot ?
Thanks in advance

Reading and writing in the Obd would be equal to the serial reading ()
Through the reading in the serial/Obd not possible to do a full backup of the ECU (TRUE)
- To make a full backup of the ECU, what you save (E2Prom-MPC-Flash but it depends on the ECU)
- Reading and writing in the Bdm allows you to do a full backup of the ECU (YOU)
- To connect Bdm you need to remove and open the ECU (TRUE)
- What it means to connect in Boot (Connect the ecu to the tour,
i.e. power it on the bench and put a specific pin to ground, allowing a reading of the Boot similar to a backup)

Right. ...

Thanks of the answers say that I am beginning to understand, so if the Ecu is not ? readable in Bdm you can not do a backup and then if something goes wrong, you can not restore the situation.

I don ? clear if the connection in the Boot ? an alternative to the Bdm in the event you could open the Ecu or not there are connections with the Bdm or simply in BDM foods only the E2prom + Flash + MPC ( I guess that is the Microprocessor) while in Boot food all ( as if it were in the vehicle).

Questions on the E2prom...

If you just need to turn off lights type drivers, service, return the value of km, you need to work only on the E2prom ?
Since I would like to try to remove a spy AirBag from a multiple of a colleague, I just have to make the backup of the Eprom and then if I do some bullshit, I can rewrite it ?

What I have in head, if feasible, would be....
make the backup with a V Digiprog 4.88 through the connector/gripper to the Eprom on the Strip, giving a quick glance I realized that you can read and save the content into Digiprog (so I make the backup), change the parameter ( I also have to understand with your help, to which address....) and then rewrite, always with the Digiprog.

If something goes wrong, rewrite the saved version, why? I imagine that the back Up full serve if you can catch it with changes in the engine mapping.

Greetings and Thanks in advance

Thanks of the answers say that I am beginning to understand, so if the Ecu is not ? readable in Bdm you can not do a backup and then if something goes wrong, you can not restore the situation.

I don ? clear if the connection in the Boot ? an alternative to the Bdm in the event you could open the Ecu or not there are connections with the Bdm or simply in BDM foods only the E2prom + Flash + MPC ( I guess that is the Microprocessor) while in Boot food all ( as if it were in the vehicle).

Questions on the E2prom...

If you just need to turn off lights type drivers, service, return the value of km, you need to work only on the E2prom ?
Since I would like to try to remove a spy AirBag from a multiple of a colleague, I just have to make the backup of the Eprom and then if I do some bullshit, I can rewrite it ?

What I have in head, if feasible, would be....
make the backup with a V Digiprog 4.88 through the connector/gripper to the Eprom on the Strip, giving a quick glance I realized that you can read and save the content into Digiprog (so I make the backup), change the parameter ( I also have to understand with your help, to which address....) and then rewrite, always with the Digiprog.

If something goes wrong, rewrite the saved version, why? I imagine that the back Up full serve if you can catch it with changes in the engine mapping.

Greetings and Thanks in advance

Thanks of the answers say that I am beginning to understand, so if the Ecu is not ? readable in Bdm you can not do a backup and then if something goes wrong, you can not restore the situation.

I don ? clear if the connection in the Boot ? an alternative to the Bdm in the event you could open the Ecu or not there are connections with the Bdm or simply in BDM foods only the E2prom + Flash + MPC ( I guess that is the Microprocessor) while in Boot food all ( as if it were in the vehicle).

Questions on the E2prom...

If you just need to turn off lights type drivers, service, return the value of km, you need to work only on the E2prom ?
Since I would like to try to remove a spy AirBag from a multiple of a colleague, I just have to make the backup of the Eprom and then if I do some bullshit, I can rewrite it ?

What I have in head, if feasible, would be....
make the backup with a V Digiprog 4.88 through the connector/gripper to the Eprom on the Strip, giving a quick glance I realized that you can read and save the content into Digiprog (so I make the backup), change the parameter ( I also have to understand with your help, to which address....) and then rewrite, always with the Digiprog.

If something goes wrong, rewrite the saved version, why? I imagine that the back Up full serve if you can catch it with changes in the engine mapping.

Greetings and Thanks in advance

Sorry ..... reading a p? of documentation I think you understand the difference between Eprom and E2Prom Flash .... so what I wanted to say above was reported to the Eprom serial that should contain the data type drivers, service, miles, that for a multi-JTD 2002 should be physically out of the Ecu in the dashboard, model 93c46 or 93c56.

Sorry for the confusion, I correctly what I would do if feasible....
I read the Eprom 93CXX with a V Digiprog 4.88 through the provided pliers, except the content inside the Digiprog (so I make the backup), I change the parameter to turn off the light on the drivers ( I also have to understand with your help, to which address....) and then rewrite, always with the Digiprog.
If something goes wrong, rewrite the original version.

Sorry ..... reading a p? of documentation I think you understand the difference between Eprom and E2Prom Flash .... so what I wanted to say above was reported to the Eprom serial that should contain the data type drivers, service, miles, that for a multi-JTD 2002 should be physically out of the Ecu in the dashboard, model 93c46 or 93c56.

Sorry for the confusion, I correctly what I would do if feasible....
I read the Eprom 93CXX with a V Digiprog 4.88 through the provided pliers, except the content inside the Digiprog (so I make the backup), I change the parameter to turn off the light on the drivers ( I also have to understand with your help, to which address....) and then rewrite, always with the Digiprog.
If something goes wrong, rewrite with the original version.

the difference between BDM and boot: ? true that in some cases the pin boot is on the comb of the ecu but we usually talk about the ecu for petrol,diesel to boot ? a point on the board(ecu opened),no ? an alternative to the BDM but it is the ecu where it's not ? the expected reading in the bdm usually puts you in the boot of the edc17.then for a backup on edc16 we talk about reading in the BDM,if we instead have to do with edc17 for the backup is in the boot. with ecu diesel pi? dated with the boot mode reads the flasks, but in these cases, usually the reading in serial or with a eprom programmer you will get the same result.
of course, they are informanzioni general, there are the exceptions...
in the ecu the e2prom usually contains data type n?frame,km,code immo,no?injectors,and not only.....
if you're talking about drivers,you have to read the e2prom internal to the centr. airbag.

So if you do not get it wrong on the ecu's dated just do a read on the serial line to make a backup to use in the restore ?