All,

I discovered another typo in the new worksheet. Step 7b should begin: "Divide the value in 7a..." Instead it read "Divide the value in 5a..." I have corrected the document and re-posted it.

 

Hi Rovin

Would it be possible to get a copy of the word doc please to get barcode for Disco 2 keyfobs. nicky@lrw.co.za is my email.

Thanks
Nicky

 

All,

I found a problem in the worksheet. I did not have the entire code39 character set. The missing character (a space) has been added and new instructions for the case where the last character of the inner code is a '0'.

The updated revision is available here:
https://landroverforums.com/forum/di...s-45057/page3/
post #23.
The new document is named disco2_fobcode_worksheet_20130403.pdf

Many thanks to Rovertechwm for the list of inner codes and corresponding barcodes that exposed my bugs.

 

Please attach the .pdf to this thread if possible.
Thanks for your hard work..
Amazing...

 

This is the latest rev of the barcode worksheet. I update this posting and the one here: https://landroverforums.com/forum/di...s-45057/page3/ when I make changes.

20130405: updated worksheet to account for codes ending in a zero

 

This is the current status of fob programming from my perspective.

We know a couple of things:

1. People have demonstrated programming a DiscoII for a plip (the fob transmitter) with just the inner key code using a Nanocom
2. People have demonstrated programming a DiscoII with the barcodes that ship with new keys using a Hawkeye
3. There is a worksheet distributed by LR that allows techs to produce the barcodes from the inner code for use with the test book system
4. My worksheet (linked above in this thread) does produce correct barcodes from inner codes on the 20 or so examples that I have gotten for testing.

We don't know yet:
1. Can the Hawkeye program a DiscoII for a used plip? Apparently the Nanocom can do this, but does it include additional features such as the ability to put the DiscoII's receiver into rolling code 'learn' mode? Bearmach states that used key fobs cannot be programmed with the Hawkeye unit, perhaps due to lacking this capability.
2. Has anyone ever used a Hawkeye to program a DiscoII for a used plip? The interesting case is a plip that was not previously known to the DiscoII's BCU or reset to new condition. Specifically:3. Has anyone used the codes produced by the worksheet linked above to program a DiscoII? Using a Hawkeye?

 

Yes. I have replaced the BCU and ECM in a 1999 D2, and with the codes I received from a LR tech on this forum, I programmed the original key, that would have been unknown to the new-to-me BCU.... all of this using the hawkeye. I have not tested with your spreadsheet, because by the time you created it, I had already programmed the keys.

On my 2003 when I needed a new key, I already had the nanocom, so I didn't try your spreadsheet... I wish I would have, I just didn't think about it.

 

Jafir, your reply gave me an idea. I had implemented the algorithm as an Octave script at first, then as a worksheet so that people without easy access to a computer could generate codes. But you referred to my worksheet as a spreadsheet. I thought, "that's brilliant!" And so I have created a spreadsheet version. Here it is:

Disco2 keyfob barcode generator

This spreadsheet is online; you can generate codes from your browser! Or, you can export the spreadsheet from the "file" menu on the page and load it into MS Excel.

 

One more note on status. I have reports of success using a Hawkeye, but the codes used were non-standard. They do not conform to the same barcode standard that all of the other reported barcodes do.

The difference is that the check characters are replaced by a '?'. For example, the standard barcodes for inner code 27821d are:
*J28721D27821CFFS*
*FFFFFFFFD87DE25*

The non-standard versions that *may* work using a Hawkeye in this example are:

*J28721D27821CFF?*
*FFFFFFFFD87DE2?*

Note: I edited this post to be consistent with roverguy7's instructions in the next post.

 

I'll be honest, I didn't read most of this thread... However, it's simple, the US spec at least.
Autologic can definitively program using the 6digit code.
If you want to get the barcodes using the 6 digit, its plugging the code in a couple times, and then through a simple cypher.
Take the code " 20C215 "... all quotation marks and spaces are there for clarity only.
First barcode always starts with " *J " then the digits " 20C215 " then the digits minus 1(I'll explain in a second) " 20C214 " then always " FF?* "
The minus 1 is applied to the last digit of the code, so a 5 becomes a 4, a 3 becomes a 2, a B becomes a A... A becomes a 9, 0 becomes a F...
" *J20C21520C214FF?* "

The second barcode get a little tricky, but still easy.
Always starts with " *FFFFFFFF " then the cypher code, I'll explain " DF3DEA " then always " ?* "

" *FFFFFFFFDF3DEA?* "

The cypher is a simple hexidecimal conversion, but can be done by hand by transposing the numbers and letters below, top row becomes bottom, bottom becomes top.

0 1 2 3 4 5 6 7
F E D C B A 9 8

Brad it look like you've spent a lot of time with this, if you are still having issues with your converter, I can email you the excel sheet from Land Rover, never had an issue with its codes.