It is good so you have ori backup .....but for emu you need original eprom. Dashboard from emu check eeprom ID from new eprom then read and write data . Solution ....new dashboard . I dont know why peaple make this job woth emu ??????
Today i did F30 2015 dash with 35160wt. Went ahead with emu which somehow killed original 35160wt chip. Luckily i have full backup including ID page so i should be able to save the dash, but when i write data to regular 160d0wq dash is only partially working (gauges not working, many error messages, mileage 0).
I checked with esys, there is no cafd. Tried to inject but finished with error.
Is it possible that chip ID is also relevant for coding, as esys sees no cafd in kombi, detects new one but wont inject it?
Should be possible to solve this with good 35160 emulator?
Original eeprom with ID page at the end attached, dump looks fine to me, i can see both long and short vin, and PN from sticker
It is good so you have ori backup .....but for emu you need original eprom. Dashboard from emu check eeprom ID from new eprom then read and write data . Solution ....new dashboard . I dont know why peaple make this job woth emu ??????
Last edited by vasa; 30th January, 2018 at 09:44 PM.
mislav88 (30th January, 2018)
Elprosys has emu where you write your own eeprom id so i dont need original eep.
It is also possible to use new blank 35160 and write id page but i dont have programmer that can write chip id, if someone has it please contact me
Sent from my Redmi Note 4 using Tapatalk
mislav88 (30th January, 2018)
The one from usprog site, with size similar to original eeprom
Sent from my Redmi Note 4 using Tapatalk
i tried a smelecom emulator yesterday on a WT chip and it worked fine, u use the original eeprom & the the smelecom 35160 eeprom adapter option
Sent from my iPhone using Tapatalk
Please hit thanks if this helped you!
Dash is alive again thanks to elprosys emulator and codiprog, it doesnt require original eeprom, only full data from it
Sent from my Redmi Note 4 using Tapatalk
Bookmarks