For those wanting more details of the fobs and barcodes.
Below is the barcodes on the right in front of the >
and to the left is the 'converted barcodes'
FROM AN ACTUAL DATA DUMP FROM A PEKTRON SCU
Data for Remote 3:
00 00 00 00 04 10 28 45 04 37 2D 9A 99 69 > N2D9A9969041028450437%
Status of Remote 3:
Programmed and enabled
Data for Remote 4:
00 00 00 00 04 10 28 45 06 70 55 A0 99 69 > N55A09969041028450670R
Status of Remote 4:
Programmed and enabled
These 28 Digit barcodes above are how they are stored in the pektron SCU eeprom chip.
Notice that the 22 digit original on the right gets 'convoluted' by taking the last 12 hex digits and putting them in front of the '2D9A9969' -the first and end charactors are ignored.( N & R) then 8 zeros are added to the front...
So, as you can see from the above, NOT having the original barcode is not really that important if you still have the SCU itself that it was coded to.....
All that is missing to reconstitute the ORIGINAL barcode is the N and last character...Nearly EVERY barcode I have seen has started with 'N'.....someone with time on their hands could via a process of elimination arrive at the proper character. Bear in mind though that it could be any of the alphabet (26) or ? . * SPACE plus 0123456789......easier of course if you have it.
A lot of the Pektron Fobs lose sync with the Pektron SCU for numerous reasons and then its time to get a new one.
The older Lucas Square ones could and can be re-synced with the 5AS