Topic

Apologies. Just one more.
One barcode starts NC####################
The other is N###D#################
Are the additional letters, C and D OK?
Or should the barcode start with N followed by numeric characters only?

it's numbers and letters and possibly a symbol at the end
You can check it here https://pscan.uk/features/pektron.html

Thanks again.
I think it is now time for trying it out. I have asked all the questions I possibly can.
I have entered both codes and started with "N" in both cases (because that is what the codes begin with).
The checker returns something like "The barcodes must start with "N", "T" or "P"").

Will report if it worked.

The p-scan successfully reported the EKA and I am pleased with that.

By way of an update a slightly frustrating outcome.

Good things:
- EKA found using p-scan
- EKA opened the car correctly (with a sweet pip of the horn when opening the door after 5 minutes wait)
- p-scan recognised the 2 working fobs during the initial "adding new fob process"
- p-scan completed the 22 character barcode for us after entering 21 characters
- the car is currently as it was before starting on adding the additional barcode (can be opened and locked with existing fobs)

Frustrating things:
- we closed the session inadvertently by pressing the wrong button on the pc
- we added the barcode and everything was going well but did not get to press the buttons on the new fob

Have we "lost" the barcode that we entered?
Or is it registered in the Pektron ECU and waiting a fob?

If it is, please can I be instructed how to link the entered barcode to the new fob.

(For info, I have another barcode and new fob which I have not touched. This barcode has only 21 characters and I assume the checksum character is a "space".)

Thanks very much for all your patience.
I am sure p-scan is a valuable tool. If only the Pektron ECU was more friendly.
I would love to be able to use p-scan more.

I don't believe that you have lost the barcode.
Either the Pektron accepted it, in which case:-
A: it is waiting for the matching fob to be used
B: if you enter it again I think that it will refuse it, because it's already been entered.

Or

It didn't accept it, in which case you can just enter it again.

The codes are only one time use in the sense that the written code matches a fob until the fob code rolls out of the window and the code changes. Unless you press the fob buttons dozens of times, the code is still valid. So only a new code and fob can be used, but, they remain new for a while, not just once.

I hope I've explained that well, I'm not sure I have ...

Watch the YouTube video that I made and you will see that I ran into similar problems, but in the end it did work.

I think that what you should do is to start the process again, with the 22 digit code that you already entered. If you get an error then that means that the code is already in the Pektron so just carry on regardless.

Thanks very much. This is helpful.

I tried to enter the same barcode again and indeed I encountered an error.

It feels like A: it is waiting for the matching fob to be used

The 2 fobs I bought came in a double SAIC plastic case with the barcodes on a label on the case. (Case means one of those vacuum formed plastic clam packages).


I had expected that one of the barcodes belongs to a particular fob but could not believe myself because there was no indication that the barcode and fob was paired.

I feel that I should have tried the other fob and I was unlucky to have chosen the wrong fob to pair.

I have seen your video and there is a lot going on. Will take another couple of views before trying again at the weekend.

The more I use p-scan, the more it can tell me about the car.

Thanks once more. I will update again.

so try the other fob?

It must be next.

Too cold and an Ofsted inspection to do anything in the evenings.
WIll update this weekend.

Thanks again for your patience and hand-holding.