Ok. I'm even more confused now. I decided to try it again ..... and it works even though it still said "programming failed" and the last digit was incorrect.
Just programmed a spare (new) red fob I've got to a 06 plated TF PScan went through the motions said all programmed and works fine. Oddly, yet again with the barcode checker it comes up with *N24195AF6744B6AAE665FM* is NOT a valid Pektron barcode but it worked fine.
I think I have spotted a pattern.
The 22nd digit on these red keydiy fobs is always an M.
am I right?
The 'N', 'O' or 'P' do not actually get transmitted from the diagnostic tool to the car, and neither is the last "checksum" character.
They are there simply to check that you entered the central 20 digits correctly.
If you want to you can select 'N' or 'O' instead of 'P', enter the next 20 digits very, very carefully, and double check them, and then commit.
You should be okay, but it's at your own risk.
Provided that you don't press the buttons on the fob two many times it doesn't really matter if it doesn't work.
so what could go wrong:-
If you press the fob buttons too many times then the rolling code "rolls" and the initial 22 digit code is no longer useful and so the fob is useless.
The Pektron has ten memory slots with two taken from the factory and so you have eight left to play with. Adding a new fob burns one of the eight. But hey you still have six left, and Technozen can clear them.
So I would say it's worth giving it a go.
I will add the 'P' in a future update.
Yes in the 90s scanners were common on the street....I owned one being a radio enthusiast...they would virtually pick any frequency that came in range of it...even mobile phones ... (not that I did😋)....the scanners themselves were harmless enough it was when they were plugged into a cub..When I was working at Longbridge the rolling code was seen as a security feature to prevent scanners getting the code. They also shortened the distance the FOBs worked to help prevent scanners picking up the codes from a distance.