XPROG-M 35080 Reads only FF FF

[se93]

Old cluster is 93C66 and donor is M35080


Sent from my iPhone using Tapatalk

[diagtech]

Ok sorry didnt realise it was older car

[se93]

No problem


Sent from my iPhone using Tapatalk

[se93]

My friend rewired and here is the read



He selected E46 M35080 and not E46 Bosch M35080 and i consider that is why the read came out as pictured with an incorrect representation of the VIN and the other data

I am going to be able to do a read later on today and will select dashboard, E46 Bosch M35080 and see what kind of read i get

What do you guys think?

Could the erroneous read have been due to the incorrect selection?

Give me your thoughts as i am very anxious for the morning here to arrive and work with this!!!


Sent from my iPhone using Tapatalk

[se93]

He soldered the wires directly to the corresponding pins off of the connector that connects to the xprog and thus bypassed the M35080 xprog green board




Sent from my iPhone using Tapatalk

[se93]

Enclosed is the M35080 pin order and the Xprog-m 16 pin connector pin labels so that the correct 7 pins can be sequenced between the M35080 eeprom and the Xprog-m special programming board for the M35080 Eeprom

I wanted to post it up in case it may be of use to anyone


I just hope and pray its a matter of selecting the correct device, reading, saving, editing, renaming/saving, erasing and verifying all steps taken and finally writing and then doing a read of the new data on the M35080 and putting back together the cluster and calling it a successful finished project!!!!!


Regards
Mark


Sent from my iPhone using Tapatalk

[se93]

Hello to all

My buddy told me he read a 93C56 placed on the DIP socket and got information from it

In my case he gets the famous FF FF

So the programmer is working for sure

Could the original data on the M35080 have gone bad somehow? He redid the read selecting E46 Bosch M35080 and still gets the FF. I also noticed the mileage reading it gives is like 40K more than what the donor cluster actually has

Any thoughts?


Sent from my iPhone using Tapatalk

[se93]

We had to remove the M35080 and read from Xprog-m DIP socket

All went perfect and now to get the cluster reassembled and installed back onto the vehicle


Sent from my iPhone using Tapatalk

[teerak2uk]

We had to remove the M35080 and read from Xprog-m DIP socket

All went perfect and now to get the cluster reassembled and installed back onto the vehicle


Sent from my iPhone using Tapatalk

Hence why I don't do these in circuit

[se93]

Hence why I don't do these in circuit

Yes indeed. I learned the hard way. Next time we will go directly to removing the eeprom


Sent from my iPhone using Tapatalk

[se93]

Yes indeed. I learned the hard way. Next time we will go directly to removing the eeprom


Sent from my iPhone using Tapatalk

I just put the cluster into the car and the LED displays says CodE

Where do i go from here?


Sent from my iPhone using Tapatalk

[teerak2uk]

ask for good dump giving details from sticker on cluster S/W and H/W engine,gearbox etc then edit the vin of your own vehicle and write to new/blank 35080

[se93]

I saved the original file on the m35080 eeprom and then we edited that bin file and saved it with another name. Then i erased the m35080 and loaded the original file that we edited and we wrote the new file to the m35080. We did a new read to confirm all was well and it was




Sent from my iPhone using Tapatalk

[teerak2uk]

post your dump

[se93]

Ok. As soon as i get back home i will post it


Sent from my iPhone using Tapatalk