Lexia reporting problems at wrong mileage

[gceau5000]

Hello,
I own a 2008 Citroen C2 VTS with almost 70000km on the clock. I do my own repairs and diagnostics and own an interface with programming capabilities. Everything works fine in Lexia, including activating/deactivating features like for example AUX-IN, shift light coding or real time parameter monitoring. The problem I just noticed is that all defects that are registered be it BSI or the general fault log appear to have happened at exactly 65545 km. This is strange because the car now has 69500+ km. I have checked the dash module (Combine in french) and it registers the correct mileage and it updates correctly at every shut down/start. The thing is it used to work fine because at around 60000km I had the classic tail light short (open circuit) and it registered the correct mileage back then when reporting the error. I initially suspected that maybe the value was stored as a 16bit integer, however 2^16 = 65536 so that doesn't explain this. Anybody else encountered this and maybe has some tips for a solution? It's quite annoying that if something happens I can't rely on proper mileage logging

[gceau5000]

OK, some more digging around and I think this is actually a normal behaviour. In the link below the same situation as mine is described. The 65545 mileage actually represents the first time the defect was detected. Hope this helps someone else too.
https://www.lemondedudiagauto.com/t2443 ... es-defauts

[GiveMeABreak]

Yes, you'll find that in the fault log of all recorded occurrences of a fault code and the mileage. It helps with diagnosis as to when the fault was first picked up and can sometimes help work out when something may of been done on a car that unexpectedly resulted in the new fault. I.e when you took it to the dealer for a service!