C5 ECU: 50 "After Sales Zone" allocations - then?

[vallium]

Might be ECU dependent but in 2.0 HDi RHR engine with Delphi DCM3.4 ECU you can certainly still erase codes. It throws some error during the procedure but codes are gone.

[Rhothgar]

Interesting. Thanks for your input.

Lexia itself states that they should be erasable just NOT memorised in the afternoon-sales zone.

This afternoon I have desoldered eeprom, soldered it back into original ECU. Soldered a sewing pin to the temporary wire I installed so I didn’t have to break into the look again.

I can verify for anyone ever having issues that immobiliser communication relies on Pin 86 in an 88 pin variant.

I can clear fault codes caused by pin 86 not being powered once I insert the sewing pin into pin 86 terminal.

I still cannot erase engine faults though they appear to be read.

A thought occurred to me that I have to manually enter VIN as it simply will not auto-detect and it should. I am wondering if Diagbox:Lexia saves fault information locally on laptop and simply checks to see if VIN number matches what you manually type in and the regurgitates the previous faults.

It goes through the motions of saying initialisation of the ECU and states RHZ Validate to continue.

I’m properly bamboozled now.

I’ve got continuity on L and K lines so it should be communicating.

I think nothing now remains but for me to get cutting, soldering and crimping and installed a new OBD socket. A job I am NOT relishing.

[Rhothgar]

Had more of a tinker last night and Lexia actually states within the interface that codes can still be erased at 50 after-sales zones but not stored.

There must be a database within a file someone with on Lexia or stored in a chip so it persists. The acid test to work that out is to do a read with someone else's Lexia and see if it recognises the car has used up the same amount of storage!

[MattBLancs]

There must be a database within a file someone with on Lexia or stored in a chip so it persists. The acid test to work that out is to do a read with someone else's Lexia and see if it recognises the car has used up the same amount of storage!

Think I can help with this query: my C5 already had a number of it's "slots" used when I first ever plugged it in - 13 or so - so it must be stored on the ECU (my Diagbox is obviously used "offline" in terms of Citroen central servers, so it has to be logged by the car).


I'm sure the "can continue clearing but not storing a record of the event" situation (when you get to / past 50 logged) was mentioned on here somewhere when I first got into playing with Diagbox.

[Rhothgar]

You're bang on, Matt.

It seems that there is some corruption in my flash files and/or eeprom.

I wonder who on here would know about configuration using Lexia.

My original ECU was mapped by a friend to 140bhp but their laptop died and the original flash file is lost in the mists of time.

Apparently, it cannot be reset to zero unless both flash and eeprom are replaced. I found an interesting post in a BMW document online which included checksums for the two types of software that the 0 281 010 251 ecu's can have.

For future reference, if anyone needs it:-

These are located in the 400BT chip. I will try and check this later but if my checksums are different I will not be able to find them. I have other Bosch EDC15C2 for which I can find the checksums and then work the HEX address that they are stored at in the bin file.

Software Reference / Checksum
1037353332 / DF3F
1037359146 / 8E6A

What is NOT clear is there is also a software version in Lexia of either 0200, 0201 and possibly 0202. They may well have different checksums I've no idea.

These seem to be the only software references for the 251 unit.