Diagbox proxy allignment after cloning Citroen Jumper 3

[domel247]

Hi there, i got customer that had to replace instrument cluster, got himself almost same that has same manufacturer and production date within months from the old one.

I copied the eeprom data from old cluster to a new one, when connected to car, the odometer changed from 375 000 kms to 399 999, after you drive one kilometer, it goes to --- --- while flashing.

I tried to do proxy allignment, but as i connected lexia and launched diagbox for jumper 3 with s.1279 adapter for jumpers, it didnt even read VIN.

After i started procedure for configuring new module, when diagbox was supposed to get configuration from BSI it failed, just as it failed when it was supposed to load configuration into a new cluster,

I dont know where is the problem, i tried to clone old cluster, but customer in between drove car with incompatible Cluster, so its quite possible that odometer data are not alligned, few kilometers with old dysfunctional, few with incompatible one.

Does anyone has an idea how to make the proxy allignment work or how to allign at least odometer, for it to not jump to --- --- after one kilometer?

Important details: -the new cloned instrument cluster is visible in diagbox, and diagbox reads part number, odometer setting, and everything.
-in attachment is reading of fault code from diagbox

[ozvtr]

I'm not absolutely sure what's going on, but the odometer reading in the BSI and instrument cluster must agree.
The only thing I would try, is zeroing out the cluster reading and let the BSI update the cluster. The BSI might think the cluster is "new" and update it.

[domel247]

I'm not absolutely sure what's going on, but the odometer reading in the BSI and instrument cluster must agree.
The only thing I would try, is zeroing out the cluster reading and let the BSI update the cluster. The BSI might think the cluster is "new" and update it.

Thanks for the answer, i thought that it should take the lower mileage and update it automaticly to the higher mileage saved in bsi. I can completely erase cluster configuration with eeprom. But i didnt manage to find mileage as i was reading eeprom, so i cant change just few bytes.