Nanocom (Evolution) Bug Report and Wishlist

I Purchased the new Nanocom Evo MK2 2 monthes ago for my Discovery Td5 2004.

First thing I tried is to program a new key in addition to the 2 working keys.
I tried to add the 6 digit of the new key in the unused slot and then made the sync for that slot.
It showed me "Key sync done successfully".
After that all the keys stopped responding and I had to disarm the alarm with the EKA code.
I did the the key programing exactly according to the instructions in Nanocom Support.

I sent a mail to Ronnie in Nanocom support he told me to wait for the new frimware which should solve the problem.
A few days ago I updated my machine with the new frimware 1.02.
It still doesn't work I tried to program each key seperately and none of them works in any of the 4 slots.

There are a few strange issues in the key programming procedure in the Nanocom Evo I noticed:

• The RF Test shows "successful test" for all the keys not matter if they are programmed in the slots or not.
• The sync fuction for each slot shows "Sync Successfully done" even if you don't transmit any key signal during the Sync procedure.
• The sync fuction also shows "Sync Successfully done" even if I try to sync wrong key into a slot(I tried to sync a key with different code than the code that was set in a slot and it although tells you "Sync Successfully done" for that slot).

I am very desperated and already 2 monthes with all the key fobs not working.

My car is with the 433mhz reciver.
My country in the BCU settings is set to UK, is it the correct setting for 433mhz reciever?
I would appreciate if someone with 433mhz reciever can get into the BCU alarm setting and write me all the settings regarding the alarm system.
I read that the previous frimware I used had some problem with BCU settings randomaly changing so maybe I have wrong setting and this is the reason that all keys don't work.

I would appreciate any help and advices which will help me find a solution for this problem!

Is there any possibility that the Key Programming module still has bugs in the new frimware 1.02 which cause my problems?

Thanks in advance

Oren

Hiya Oren

Quote:

---

Is there any possibility that the Key Programming module still has bugs in the new frimware 1.02 which cause my problems?

---

Sadly yes.

It seems that you cannot make an omlette without breaking a few eggs.

I have posted up our troubles with testing this Key Programming stuff, which despite my finding our Disco 3 Receiver and wiring it into our Dico 2 bench jig, did not produce the required result and help us determine if key fob programming was now working as it should. Although we had no Beta tester feedback, with all the other stuff we had to release, we did take a bit of a Punt in that our latest changes to the Key Fob programming stuff might fix it. But clearly it has not and has even made matters worse for which i can only apologize.

The good news is that we are very committted to getting everything right and working as it should, and as such i have purchased a genuine Disco II receiver off Ebay that is now winging it's way to us.

Come hell or high water, we will get this right on the nanocom and just beg a little more patience of you.

Just small info - my friend understand english only with help of Google translate. And yes, we are changing emails with guys from BBS, to find the solution.
I understand fully, that without some test jig on table, it is a bit hard. I have this jig for TD5 ECU - for testing and repaing ECUs. It takes too much time, to do the testing in real car.

Just a quick heads up on where we are now at with fixing this most evasive and elusive Key programming problem.

We have traced it down to a simple procedural error that after programming a Key, overwrites the Synchronization, causing a loss of sync with it and it to not work.

Having fixed that in the software, we sent a copy to a beta Tester with a vehicle, who reports they have now happily programmed 3 keys into it without any problem :D

But in addition, late this afternoon the Disco II receiver I bought on Ebay, that looks identical to the Disco 3 one we have been using unsuccessfully on our own test jig, finally turned up. :cool:

It took a bit to hook it up as we don't have a roof loom with the connector for it and are having to resort to soldering wires direct to the receivers PCB and hook it straight into the BCU.

But it was all worth it in the end, as lo and behold, it actually worked [bigsmile]

Our BCU is now responding on the Key test as it should and everything is clicking away when we press the fob's buttons and there were some high fives all round.

Tomorrow we will program keys to double confirm that function is now all fixed and working properly before finally ticking that troublesome job off the list.

However we do not intend to make a release just for this fix alone, and so we are also working on a small number of bugs that have been reported on the Motronic and Auto Box, including the live data reading crashing one for the Auto Box.

In addition we have now very nearly reached the Beta Test stage of adding our P38 Coverage for the Nanocom that i mentioned and posted pictures up of in my Blog

http://www.aulro.com/afvb/blogs/bbs+...pment-p38.html

Having a P38 vehicle myself, and them being very plentiful here in all their variants, I really do not imagine anything like the same kind of problems we have had debugging this almost embarrassing Disco II key programming fiasco and I really want this P38 Coverage to be available before Dec 1st, even if it may still have a small bug or two to be sorted.

Which will be nice, because TBH, if you had not already noticed, we really do totally enjoy the challenge of getting things spot on right here ;)

With the help of guys from BBS the bricked Nanocom is again working. Detailed description how to do it, will be published together with the next firmware update.
Thanks for help

Quote:

---

Originally Posted by BBS Guy

Just a quick heads up on where we are now at
However we do not intend to make a release just for this fix alone, and so we are also working on a small number of bugs that have been reported on the Motronic and Auto Box, including the live data reading crashing one for the Auto Box.

---

Hi Colin,

As I wrote I am more than 2 monthes with my alarm system not working because of the bugs in last firmwares.
I am waiting poor forward for the coming firmware which might solve the problems and reactive the alarm system in my Disco 2.

I would appreciate if you can release the coming firmware as soon as possibe or even if you can send me a beta version personally.

Thank you very much for your assitance you are doing wonderful work.

Best Regards,

Oren

landmotors@gmail.com

Another thanks to BBS and colin for there efforts,

Has any body else had the EVO 1 freeze whilst writing maps,:o Mine has done it a couple of times; I have found if you give a 5 second gap after every opperation and touch of the screen all works well every time:cool:

Anthony

Which firmware are you using ?

Quote:

---

Originally Posted by peter5111

Which firmware are you using ?

---

I am using the last firmware 1.02

Hi Colin,

I updated my Nanocom Evo mk2 with the new firmware 1.03 you released today.

I again tried reprogram my keys with the BCU and it still doesn't work and the car doesn't respond to any of the keys.

My car is a 2004 Disco TD5 with the 433MHZ alarm frequency.

What else should I check that you think can cause the alarm not to work.

Can you list all the correct alram settings for my car maybe something is wrong with the settings.

Before I tried programming my car with the Nanocom the alarm system worked perfect, Since I tried program my keys with the Nanocom the alarm stopped working(3 monthes ago).

I would appreciate your help.

Oren