VW Passat B6 - 1.9TDI BLS soft put into 2.0TDI BMP ECU Help!

[WinWoj]

Can I put flash data from 1.9TDI B6 BLS, to ECU from 2.0TDI B6 BMP? Because I have BLS engine, but I don't have ECU from BLS, only from BMP. Reflash via BDM is enough?


For example, when I connect ECU with orginal BMP 2.0TDI EDC16U34 to XPROG-M and read data, then can I write eprom from BMP 2.0TDI and flash from BLS 1.9TDI as one BDM writting? Please help me, because new ECU from BLS and immo job will be more expencive I think..
The reason is engine swap from 2.0TDI (was broken) to 1.9TDI (new one) both edc16u34.

[Babos]

If ecu hardware is same (bosch numbers to) 90% all be ok.
Replace full.

[ZIZZOU]

you can't m8

[WinWoj]

you can't m8

Zizzou, could You explain me why? In flash memory are maps. In eprom is ecu numbers, VIN, and maybe im*o (i'm not sure), so If I leave old eprom, but BLS maps change, why car will not run?

[ZIZZOU]

becose the hardwarde of the 2 ecu are different
so you can't change the software between them
you can make a clone of ecu if the 2 ecu have the same harware number

[WinWoj]

OK, I understand. But I check both outside area of BMP and BLS, the same pin description, all sensors and actuators the same. Only volume different. I didn't see pcb laylout of BLS ECU, so don't have this knowledge before... But, how You think, if I will change software, I should change only flash, or flash + MPC configuration? Could someone take foto of BLS ECU?

ECU number of BLS: 0281013437, 0281013620.
Thanks

[radioman]

Hi,Try to bdm100,must correct chk.I had problems with x-prog with BDM was fine

[WinWoj]

Hi,Try to bdm100,must correct chk.I had problems with x-prog with BDM was fine

I haven't BDM100...

Some people read and write BDM via XPROG-M with succes.. I saw, after readout eprom 95320, then data in some adresses was changed - during first readout and then verification was errors, few bytes add +1 value. 2nd readout changed also +1 the same addresses, but 3rd readout was without changes. So 3rd readout via Xprog = 2nd. Im flash I saw only 1 byte changed, comparing 1st and 2nd readout. 3rd was the same as 2nd.

The problem is, that after 1st readout flash and eprom via XPROG, i lose communication with ECU. Before BDM readouts I successfuly connect KTS 550 to this ECU and read id, erroes and data. After read data via Xprog, I can't talking with ECU.




What could have happened?

246776 246778

[filecloud]

0281013437, 0281013620.
Thanks
Both ecus are exactly same hardware: EDC16C34-3.42
Use good BDM100 for cloning or you run into Problems!

[WinWoj]

Both ecus are exactly same hardware: EDC16C34-3.42
Use good BDM100 for cloning or you run into Problems!

You don't understand. I need one of this twoo BLS ECU foto!!!, to visually compare with my BMP with ecu number 0281012119, as I have.

I must then compare 0281012119 with (0281013437 or 0281013620). Zizzou wrote hardware is different, so it can be difficult or immpossible to
swap flash data from BLS to BMP ecu... But now I cannot check tis, because XPROG modyfied my eprom during readout, and probably this is cause,
I lost communication with KTS 550...

I writting in this moment flash and eprom data from readout nr 1, without verify, to get possibility comunicating with ecu via obd diag tool..

Maybe xprog is not usefull in this edc16u34 system, but few person from dk was succes with moding them...

[WinWoj]

Guys, reprog to orginal (i think) 1st readout doesn't solve my new problem... I haven't comminication with KTS 550..
Is possible to change some options in xprog, to do good job them? I haven't BDM100, and as I read before
threads about using XPROG to BDM programming, people wrote then it working... Why in my case no?

[radioman]

After write MCP Flash EEprom use checksum button...if not correct checksum ecu not ok....

[filecloud]

Hello
0281012119 also is exactly same ecu: EDC16C34-3.42. No picture needed. Hardware is 100% identical. Stop playing wth xprog. This is crap. Use good BDM100 tool and do a full clone. EVC BDM100 is best choice. Job done.

[ZIZZOU]

I haven't BDM100...

Some people read and write BDM via XPROG-M with succes.. I saw, after readout eprom 95320, then data in some adresses was changed - during first readout and then verification was errors, few bytes add +1 value. 2nd readout changed also +1 the same addresses, but 3rd readout was without changes. So 3rd readout via Xprog = 2nd. Im flash I saw only 1 byte changed, comparing 1st and 2nd readout. 3rd was the same as 2nd.

The problem is, that after 1st readout flash and eprom via XPROG, i lose communication with ECU. Before BDM readouts I successfuly connect KTS 550 to this ECU and read id, erroes and data. After read data via Xprog, I can't talking with ECU.




What could have happened?

246776 246778
xprogm had KILL you ecu:guns:
buy an other one,
buy a ecu for your new engine and make immo off
it's so easy m8

[WinWoj]

Yes I know that was so easy, but the man, who give me this ecu told me that this job could be cheaper...
I known that it would be not easy way, so I was risk.

Now he know, that must buy properly ECU, but I want to restore comunication with this ecu.

XPROG worked very well till today... This MPC project shown me, that is not so good I thought..

OK, software is killed, but electronics not. Maybe BDM100 can enlive it.
I'll try, but must have MPCprog or such like that.

Regards.