bigbear (7th January, 2024)
hi all
ive just got a bmw from panel shop and odometer is 9999999
i do not know history of cluster but the chip looks like solder is not factory
the car is a 2009 bmw 320i e90 LCI petrol engine
here is the orig dump and the dump i modified to try match up to the cas3
cas3 i read using digiprog 3 just so i can get the km reading and it has 46865
so i then read the cluster which had 46683 which i saw there was 200 kms differnece
so i decided to program the read from the cluster to match the cas3
i am still getting 99999 so can anyone check these 2 files and see if the checksum is wrong
the cas 3 is 46865 so i need the cluster to be the same
if anyone finds an error can u please fix the file
thanks
bigbear (7th January, 2024)
First Dump was wrong.
your dump is correct!
i will say your eeprom in dash is Damage.
buy second one and write dump and solder back in dash with new eeprom
buy another dash?
my dump i write to new chip and i solder onto board
odometer is still 99999
and tamper dot is on
and needles dont work
maybe i didnt solder it on good
i will try resolder and also try another new chip
if my dump is good must be something else
can cluster be faulty
digiprog read cas plug or obd or st52 on cas put zero no another mileage but i thin you damage cas with digiprog put zero in cas put zero i cluster post backup files from cas tachosoft iisnt good calculator you can not check wath for version algo
put HW and SW No. of the instrument cluster on here and maybe someone my have a good image that you can then hex edit to input the last 7 digits of your chassis no and correct mileage/km..
Your tachosoft eeprom seems good and shows 46864km.
Ckeck your 1st pin eeprom - may be u solder vise verse , check solder on legs eeprom
Check that the eeprom is soldered in the correct position.
It usually shows 999999 if the eeprom is not soldered at all or soldered in the wrong position.
I know exactly what is problem because I had a same situation a month ago. I can bet that your display showing 999984, not 999999, am I right?
A both files are 100% good with a little difference in km.
You need new 35080 for dash, that one is damaged, when you done all, check lws you will see the fault code
Last edited by sida; 21st January, 2018 at 10:19 PM.
does the dumps in the cluster contain the vin
im wondering if the panell shop change the cluster and its not vin matched
if the dump has the vin can u tell which lines it in
thanks
Can u post , the eeprom data from cas?
When read eep. from CAS dont kill this..... because killing this very very simpel........if you not have experience with this ,dont just touch this......................
If samething wrong,you have problem like this and game over.
http://www.digital-kaos.co.uk/forums...ns-error-after
Last edited by brend; 22nd January, 2018 at 10:23 AM.
NB!!! Don't ask in PM old file password , Im not remember.
You resolder your eeprom?
Your VIN from Car?
I say again the Problem is your EEPROM, this is Damage
sagie1zn (22nd January, 2018)
hi bersch
the chip on cluster looked like had been soldered
so I do not know what someone else did before
I read the chip and modified the kms to be close to the cas
then I flashed a new 35080 chip with the dump using my upa clone
then I soldered it
sorry I don't know if dash is from another car
if the car comes back ill get the vin
and ill remove chip and resolder and try again
its hard trying to fix a car someone else has touched
thanks all for the help
It does not have to be touched to get that value on display....
I told you, your chip is bad, take another one, your dump lws is also damaged it is showing lws wrong id...
Take new 35080 good quality
Bookmarks