Let's try what I asked first, I will try to explain again, in more detail. 😀

Please go to controller #5, and click on coding II -11 or coding -07 (whichever works) and the window will pop up, and in the window you will see all the blue zeros, but when you hover the mouse over the zeros a balloon will pop up showing the login code as I showed prior and will now show again circled in red, please input the code "19795" as shown in the attached picture, OR what ever code your end shows into the box, then see if you can input the proper coding of module and workshop number as shown in your previous picture when all information was shown, I have attached that also with the red dots showing you part number, soft coding, and workshop number.
Please try this before anything else.

Johnny

.

 

Like this.
Sorry, this is on my cellphone, I can not make the drawing font smaller.

Johnny

.

 

here is what I have
Also can you please tell me how to enable automatic display of pop-up window help

 

I would try once more, with leaving the leading zero off of the software coding, so try 143597.

If that fails, then I have no clue what you did to remove all the information of VAG number, software coding number, workshop number, VIN , etc. especially on what you say is the original dump BIN file, it was there before as shown in your previous pictures, so you wiped it somehow between your friend's bench work, and ODIS...

You are using the original 93C86 chip and not a new one, correct ?

Because,
You have me somewhat confused as you either mis-state or typo some items at different times, you call it a "93C56" it is the 93C86 just to be sure that you have the correct eeprom.

Then you say that you have the original dump, and the dump your friend did I believe while working with ODIS instead of Ross-Tech, BUT, then you say "Replace the Original eeprom", the eeprom itself is always original, just the code on it was rewritten by your friend, OR, is the eeprom not original and you both wrote dumps to NEW 93C86 eeproms ???

If it is the original eeprom chip,
As you say, your only next move would to be to write the second dump BIN file from your friend back onto the eeprom, and verify no countdown, then try to program just 1 key.

It would make no sense I believe to as you said, to put the second dump file on the eeprom, verify no countdown, then remove the eeprom and re-write the void of information original dump BIN file back on again, you would be right where you are right now, with all the field blocks zeroed out.

Johnny

 

No luck: for 143597 I have error SWC 143597 is invalid must be 7 numeric digits
For sure I am using 93C86
No choice back to te bench.
Will inform you when everything is back.
Thanks for your patience.

 

@kilog ,

I just went back and read this from the beginning, and something just stuck out like a sore thumb...

Are you using a legitimate software version of Ross-Tech VCDS, and a legitimate Ross-Tech VCDS dongle (hardware), or have you switched between two different pieces of Ross-Tech hardware or software, because something is not right at all with the software display of measuring blocks channels 22, 23, or 24, as all the blue writing of descriptions for each field is gone in all of your latest screenshots, along with all the missing vehicle information, yet in your previous screenshot all field descriptions were present along with all the vehicle information.

See your pictures comparison.

Johnny

.

 

Ok,
A little update as to why all the blank field descriptions in measuring blocks, I just had a nice long talk with Tech Support at Ross-Tech, and the consensus is, as all the information for the KESSY module was available for Ross-Tech VCDS in your previous scans as shown by the available VAG number, VIN, and IMMO ID, along with workshop code, and so on, then the RT VCDS was able to apply the proper [Label File] to overlay the measuring blocks descriptions (the blue writing).

BUT since you had some kind of mishap during yours or your friends reading and writing of the 93C86 eeprom, which in turn left all the fields for VAG number, VIN, IMMO ID, workshop code, and so on all blank with zeros, then because there is no VAG number of the KESSY module for the Ross-Tech VCDS to read, it can not put a label file overlay onto the measuring block fields..

He also stated that, being that you were successful in accessing the KESSY Module with the pin code, and then we're able to pair all 3 keys to the vehicle, and have each key power up the dash and unlock the steering column, then all programming went as it should, and that most likely the real issue you have is a faulty KESSY module itself, as in, once you were done and took the last key, none of them would work again, so if you were to read the 93C86 eeprom again with carprog, you would probably see all the key blocks blank again.

You never did say if the engine ever started, or if you even tried, just that the dash lit up and the steering column unlock.

I would be reading the eeprom again for key information present or missing again.

Johnny

NO VAG NUMBER, NO LABEL FILE OVERLAY



GOOD VAG NUMBER = GOOD LABEL FILE OVERLAY.

.

 

Hello Bro,

Thanks for your findings, it also confirme what I learnt from VCDS manuals about Labels when it is not not documented.
Here is the Original eeprom back.
It took some time because I had to replace the 93c86 because of a broken leg. What is in now is a new one.
the display of 24 block is 0, 0, 10, 255 => the Ecu is bloked again for 4h.
I still think that immediate swap of dump after introducing wrong 7 digits pin code was the big mistake.
Something inside the Kessy module may memorize the lockdown of the Kessy, and for me I suggest to endup the present countdown and restore the dump that was on during Odis session,
Then wait the countdown and after that, restore the original dump.
Anycase, as you said from in your last post there should be something wrong with this Kessy, otherwise it should have accepted the 3 keys programmed... so at last we may have to change it.

History of the car: the car is in a garage and has been there for close to 1 year, it came for trouble in the suspension and for painting.
Then the mecanic found a leakage beneath the dashboard in the bonnet engine and had to replace that water tube just down the windscreen, and to do that he has to remove the whole engine.
after that the car has not start.
I did not witness all this, I just was be reported it.
When I got invloved in this issue, the ignition was coming, and the steering column was opening as well.
The comment I cane make is that technicians in the garage does not consider how sensitive Bentley is with batteries...
Thebatteries are moved from one car to another, the Bentley does not have its own batt. and its can be swapped or jumped carelessly... This also may be the origin of this disorder...

 

I am at a loss for words, taking batteries out of a customer's vehicle for use elsewhere, then throwing any old battery back and forth into the vehicle, sad, and just wrong.

Please clarify these issues for us.
The vehicle has been at the shop for a year, I assume it came with it's own 2 batteries ?

The engine was removed then reinstalled, and at that time the keys still worked for turning on/powering up the ignition and instrument cluster, along with unlocking the steering column, correct ?

If the keys still worked as described above, why was the KESSY module ever touched, did they ever try to start the engine, if so, did it failed to run, or even crank over, or did it start and die after 2 seconds ?

Also if you read the screenshot of block #22 that you just posted, #22 third block over shows the key as "NO", as in the key is no good, as block three's question is, "Key Condition OK ?", yet in the beginning when your screenshot showed all the proper information for vag number, VIN, wsc, etc the answer for block #22 third block was "Yes", so the key was good, SO, you either used a different one of the 3 keys, or 4, as you switched a few times from 3 keys to 4 keys, so I do not still know the true number of keys to tried to pair to the KESSY module.

I also said no to the 7 digit pin, but it appears that you did it anyway with the wrong pin..

And now you had a broken pin/leg on the 93C86 eeprom, and your latest screenshot still shows all the vag number and VIN as zeros, that is not good, as the required information is not there.

The broken pin is most likely how you lost the proper bin file, at least my thoughts.

The next problem is, if in-fact you or your friend have corrupted the bin file in anyway, it is not useful to use in any replacement KESSY module, as the required info is gone, your would be putting the same no good bin file onto the replacement KESSY, and would be just where you are now, if this is all how it is, you will need a brand virgin KESSY module from the Bentley dealership to put in the vehicle, as you can not clone a used KESSY with the bad bin file you most likely have.

I ask that you upload the bin file here as an attachment, or I will PM you my email address to send.

To be honest, I have tried my best to help you, the history of the vehicle should have been the first bit of information you should have shared, like I asked you for back in post # 10 and again in post #38, we are now at post #86, along with staying on one track instead of so many tangents.

I await your response to questions, and the bin file.

Johnny

 

Hello friend,

Here is the Original Kessy dump.
I have sent the password is your mail box
With this file I was able to open the steering wheel.
For me this file is Correct and is restored without problem, but I am surprised to have another result on the car
To solve the issue, maybe we could try to virginize the Kessy and put this file back.
or to buy a second hand and put this dump inside to start the car
Thanks one more time for your help

Kilog

 

Hello @kilog ,
Sorry I could not answer, I am working right now.
I did try to call you, but then it was either midnight or 1 in the morning for you... sorry

I think you are correct in that the bin file looks good, BUT with 1 hiccup I see, and I am not even sure it is a problem, but it does differ from my old 2005 bin file, as in line 0000003F shows the part number "3D0909135R" for both of us, so that's good.

Line 00000127 shows our VIN numbers in the proper format for both of us, so that's good.

But,
Line 00000492 on your bin file has a space in the VIN number, see pictures.

Whereas my line 00000492 has no space in the VIN number.

Just thinking of everything I can, as you said, yes if yes bin file is all good, then by all means get a used KESSY and clone it, BUT you MUST get the same exact part number with matching sw and hw numbers, no prefix X or C , just exactly what you have, BTDT...🤫

Again, I do not know if the gap in the VIN is an issue, but I would be looking at it, maybe writing a copy with no gap in VIN and giving it a shot.

Johnny

.
Removed pictures by request, VIN security.

 

Any updates @kilog ?

Johnny

 

​​​​​​Hello @kilog ,
Please keep your responses here in the forum instead of private messaging me, this way all can read, help, learn.

ALSO, PLEASE answer my questions in prior posts, but most importantly, as to my question of, did the engine ever run after the engine was installed back into the vehicle, there are many reasons for asking this question, so please answer it.


Sorry, but no, you can not use my dump file as my file will not match your keys, ignition switch, steering column, or the twin engine ECU'S,
as far as making a Kessy virgin, I have not done that, I have only cloned a Kessy of the same exact part number with the bin file of the vehicle being worked on, therefore the keys, ignition switch, steering column, and engine ECU'S all are matching.
(except for my 2011 Supersports engine ECU'S, but that's a different story) 😀

You can do a used KESSY of the same exact part number, you need to get pin from both KESSY module's 93C86 eeprom, being you have the pin already for your original unit, you would then read the pin of the used (Replacement) KESSY module's 93C86 eeprom, then use both pins codes as required to replace the KESSY module and do adaptation of the KESSY with Ross-Tech VCDS, meaning, NO writing of any dump BIN files at all, although, some say to go this route with both pins, others say,
if you are going to read both pin's from e-prom on the bench you can just swap eproms, then no adaptation of the KESSY module itself is needed as you have put your original eeprom or dump file into this replacement KESSY, either way you decide by both pin method or swapping of eeproms, you then after will just learn the keys back to the vehicle, I have done the swapping of eeproms method with single pin code, in the future I may try the 2 pin code adaptation method.

Again,
You will need to get an idetical kessy as there are difference in the H/W specily with keyless go function many think it's just a coding variant where the real diffeence lay in the H/W + Coding

If cloning the KESSY does not work for some odd reason, then you will need to order a brand new KESSY module from the Bentley dealership by VIN.

Or you have to find a package deal like this on eBay which is for a 2008, so find a 2005-06 package, that will consist of the KESSY module, steering column, keyfob, ignition switch, and the twin engine ECU'S, as these all need to be paired together from the factory.

https://www.ebay.com/itm/06-07-08-Be....m46890.l49292

Also, let's keep this in the forum so all can learn together.

Thanks
Johnny

 

Hello Johnny,

I know I cannot use four dump
the idea was to compare both file as you did and see if i have the same result with at offset 00000490.

Fom my point of vue I think either the Kessy has an internal fault which prevents the Dump from being loaded correctly by the VDCS, or the Dump has been incorrectly read by Carprog and is no longer really the original each time we try to restore it.
I have ordrered a used Kessy with the same exact part number.
As for me I prefer adaptation way to install it when it will be there.
But I have a question:
Is it possible to try adaptations between a malfunctionning Kessy (not showing VIN and partnumber in VCDS even if they are available in the Dump), and a used one with both pin number available

Regards
Kilog

 

@kilog ,

Maybe your comments get messed up in translation...

But again, it was not line 490, it was 492.

Next, the dump does not get loaded with VCDS, it gets written to the eeprom by either carprog or ponyprog, VCDS does not read or write the dump.

Next, that is what I have been trying to tell you for some time now, that either you or your friend fouled up the 93C86 eeprom dump file somehow, BECAUSE, when you first scanned the KESSY module with Ross-Tech VCDS all the pertinent information such as VIN, IMMO ID, and PART number were all available and visible as previously shown by you.

And lastly, forget about the no good KESSY module, pretend that you don't even have it, it is not in the vehicle, BUT, you have its pin, and you will need to get the pin of the (USED) replacement KESSY by reading the 93C86 eeprom just as you did to get the original pin from the now dead unit, then follow the instructions as shown in the video, there are two versions of doing this, so watch the video closely, you will install the replacement KESSY module into the vehicle, you with then scan it with Ross-Tech VCDS, you will then click "Security Access-16" to get into the replacement KESSY module and input it's own pin code, then proceed to adaptation using the original pin code from the original KESSY module.


Johnny