Ok; I have followed the Black Box video religiously....

I have a chip with 6 digit code.
my chip says it is 315mhz.

I have success up to the point of the FOB being detected after the sync. The FOB will not detect.

there are 5 slots on the NanoCom key page; are there too many keys in the BCU? I tried deleting them but the BCU adds them back when it updates.

I used the 1 and 2 slots replacing old codes with the new code and it would not detect the FOB in either slot after the sync.

does anyone have a reliable source for 315mhz chips that are known to work for members of this forum?

I’ve been dicking around with this key for a year. It was supposed to be a genuine LR key, bought from Rovers North; LR of Louisville couldn’t program it because they wanted the barcode...I do not have it; lost the damned thing.

doc

 

Are you sure you have the correct 6-digit code for the fob?
Verify this is what you are doing...
https://www.nanocom-diagnostics.com/...CU%20Guide.pdf

"KEY PROGRAM 6 DIGIT INNER CODE (Used on the Nanocom Evolution Mk 2)
This function allows you to program one or more keys on the 4 slots available (the suspension plip is not used) by means of the 6 digit code printed on the label of the circuit inside the fob. The code must be written in the desired slot and confirmed with the corresponding button. We suggest using the first slot available. Once the code is inserted and confirmed the SYNC KEY function is required to synchronize the fob’s rolling code."

I also found this on the AULRO website...
"1. Open the ignition key fob and remove the circuit board and battery in one piece.
2. Write down the 6 characters printed on the chip on the underside of the circuit board. If you have another working key, keep it handy with the non-working key
3. Start Nanocom and select the Valeo BCU tab
4. Select "Utility" from the left pane
5. Perform an RF test with the working key. A success message will be displayed stating the key number
6. Select “Key Inner Codes” from the left pane of Nanocom
7. Click “Update” to display the codes stored in the BCU
8, Enter the number from step 2 into any of the key fields, except the field which is the one for the working key identified in step 5
9. Click “Set Code” next to the field you just added the key number from the non-working key.
10. Click update and check the new number was written to the BCU
11. Perform the "Key Sync" function
12. Disconnect Nanocom and check that the key works"

 

yes I have performed the operation correctly; yes I have the proper code supplied on the back of the chip.

there is a step missing in your quoted process; you also have to apply the key detect function after the key sync.

the key scyncs to the BCU bit is not detected afterward.

here is the video of the process.

 

See if this helps:


<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-parent:"";
margin:0in;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-style-unhide:no;
mso-style-qformat:yes;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
mso-add-space:auto;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
mso-add-space:auto;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
mso-add-space:auto;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
mso-add-space:auto;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
.MsoChpDefault
{mso-style-type:export-only;
mso-default-props:yes;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1979992938;
mso-list-type:hybrid;
mso-list-template-ids:-329582344 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}

-->

1. Discovery II

2. Motronic

3. Valeo BCU

4. Second Page: Key Programing (will show “Working” and then “Function in progress…”bar will be shown. Then it will display all the fobs coded to the vehicle)

5. Find slot you want to replace

6. Choose slot, press where numbers are. This will bring up a key pad. Used backspace button to delete the numbers for that slot, enter in new key code, press OK on the key pad.

7. Press Set button next to the slot you were just working on. It will show “Function in progress…” bar will be shown.

8. Next scroll to second screen and press SYNC button next to slot you were working on.

9. Nanocom now asks you to press on of the buttons on the fob then press OK on the screen, “Function in progress…” bar will now be shown.

10. Press OK for the screen that says Key synch successfully completed

11. Press KEY DETECT button, “Function in progress…” bar will be shown.

12. Asked to press a button on the fob again. Press OK button after doing so. “Function in progress….” bar will be shown.

13. DETECTED will now show in that slot and you are done.

 

ken

i couldn’t even get to your post information; some error in your linked info created a massive page coding error...

at any rate I posted the link directly to the Black Box video...the people who make the NanoCom....I followed their steps explicitly and...no joy.

i have determined, without any evidence, that either the chip is faulty, the code on the chip label is wrong, it is an aftermarket Chinese chip, or it is not an actual 315mhz chip.

i wish there was a way to obtain the actual chip code from some means; I’m sure there is a device that you can use to actually obtain the code...but I do not know what device you would use or the process required.

thanks for trying to help.

doc

 

I know you're not blaming the Nanocom, but FWIW Ken and I can attest that the Nanocom you have in hand can program a keyless entry fob. We used it to do one for me when Ken rented it a few months ago. I'm sorry you're having so much trouble.

 

Yeah I've used mine to program Fobs that even a T4 LR unit had issues programming. Only time I've run into issues = not given the 6 digit code or the MHz was incorrect. Sorry it's being a PITA.

 

oh, I have no doubt that it is the key; not the NanoCom.

as I said I think it is either:
a dead chip
a knockoff chip
a 433mhz vs 315mhz chip

When I bought this key it was supposed to be a used key that needed to be reprogrammed. i am leaning towards a combination of the last two; I think the seller put a knock off chip into the OEM case and sold it to me as a used key; and that the chip is 433mhz, which is why it will not detect the key after the sync.

we shall soon see; I bought another key today will be delivered over the weekend. I’ll program it and be done with it.

i have been fighting with this fkin’ key for almost two years....

 

Test the Fob frequency on an AM radio or TV to see if it even works.

 

I'm not sure why my last post had all that extra data. Those instructions were copied and pasted from a Word file I created that is the instructions from Blackbox's YouTube video.

Anyway, seems there are lots of bad fob chips out there especially sold on ebay.

My recommendation would be to see if you can return the one you purchased and buy from Atlantic British or Classic Rides of North Wales crnw.co.uk or Island 4 x 4 also based in the UK.

About $160 plus shipping from the UK and they are Genuine Land Rover