Thread: Nanocom (Evolution) Bug Report and Wishlist

Originally Posted by BBS Guy

Hiya Oren

Nah, trust me, It works

It's almost certain that you just have a procedural problem.

I had one of my chaps knock up a quick demo video for you today, showing the procedure and it actually working on our test rig. He first programs a key's code in slot one, shows it being synced and detected, then erases it back to the old value showing it no longer being found, then programs it into slot 3.

It's a bit big, and i could have compressed it and lowered the resolution to host it on our site, but then you might have lost some detail, so i have uploaded it to Youtube.

Here is the link to it.

Disco 2 Key programming - YouTube

Let us know how you get on.

Hi Colin,

Thank you very much for your detailed video.
I tried the programming procedure according to your video.

In the end god bless it worked just for 1 out of my 3 keys.
The 2 keys that were orignally programmed and worked with my car didn't work(These are the 2 keys that worked before I tried the Nanocom).

The new key(third one) that has not been programmed with my car yet worked and managed to activate the alarm.

I tried to program another friend key(fourth key) that also has not been programmed with my car and it also worked.

I tried to put a new batteries in the 2 keys that still don't work and it still doesn't work.

In my opinion there are two possible options for the 2 keys that still doesn't work:

• I destroyed them because of the many attempts I have tried before to reprogram them.
• There is still a Bug that avoid these two to be programmed as well, because they were previously programmed with my car.

I have to try these two keys in another car in order to figure what is true.

What is your opinion regarding this issue?

Thank you very much for all the help and wonderful work.

Oren

Hiya Oren

Well i am glad the video helped you to make some progress at least.

I am quite sure that there is no longer any bug in the software.
It's really quite bad enough that we had to have more than a couple of goes at sorting this, which was really only due to a lack of our having a fully working test rig in this respect at the time we had to release the upgrade with our second attempt for the other things it contained.

As you can appreciate, we have a huge reputation and history for being the very best there is with this kinda stuff and we are certainly not typically producing software we just hope works, or is in any way iffy, intermittent or borderline.

In fact i have a very strong held belief that any test equipment must be absolutely utterly dependable. It's bad enough looking for a problem but to be doing so with something you cannot absolutely trust and believe in what it is telling you just makes things even worse.

I really do not see how you could have possibly destroyed 2 keys.

My best guess is that somehow or another you are now entering the wrong codes for these two keys.

Where did you get their codes from?

Originally Posted by BBS Guy

Hiya Oren

Well i am glad the video helped you to make some progress at least.

I am quite sure that there is no longer any bug in the software.
It's really quite bad enough that we had to have more than a couple of goes at sorting this, which was really only due to a lack of our having a fully working test rig in this respect at the time we had to release the upgrade with our second attempt for the other things it contained.

As you can appreciate, we have a huge reputation and history for being the very best there is with this kinda stuff and we are certainly not typically producing software we just hope works, or is in any way iffy, intermittent or borderline.

In fact i have a very strong held belief that any test equipment must be absolutely utterly dependable. It's bad enough looking for a problem but to be doing so with something you cannot absolutely trust and believe in what it is telling you just makes things even worse.

I really do not see how you could have possibly destroyed 2 keys.

My best guess is that somehow or another you are now entering the wrong codes for these two keys.

Where did you get their codes from?

Hi Colin,

Thank you very much for your reply.

I got the codes of the 2 keys from the inside label on each key(The label is found on the chip itself).
Key 1 : 40C36C ( I tried also O instead of 0 just in case and it still doesn't work).
Key 2 : 3A3E49
I typed the codes with capital letters.

Is there any way that the Nanocom can get a key signal and write his code?

Thank you very much for your help
Oren

Colin,

Thanks for the video, I followed it and I was able to sync a new fob with ease.

Roger

Hiya Oren
No worries, here to help if and where i can

They are hexadecimal, so its definitely a numeric Zero rather than an alphabetic type "O"

Sometimes we see problems that are related to hex values below 9, ie with a preceding zero that gets lost in translation.

IE a code of 123409 is broken into 3 bytes of 12, 34 and 09 but ends up when joined together as 12349, but we are pretty old hands at this here, and as long as the code is not written prior to our morning coffee on a Monday, does not typically slip by us

As unbelievable as it sounds, it really does seem like you just have a couple of now non working fobs.

There is no way we know of to figure their codes out from the transmitted signal they produce, if indeed they are now even transmitting anything.

Sorry i can't help more

Roger
Glad the video also helped you

Originally Posted by BBS Guy

Hiya Oren
No worries, here to help if and where i can

They are hexadecimal, so its definitely a numeric Zero rather than an alphabetic type "O"

Sometimes we see problems that are related to hex values below 9, ie with a preceding zero that gets lost in translation.

IE a code of 123409 is broken into 3 bytes of 12, 34 and 09 but ends up when joined together as 12349, but we are pretty old hands at this here, and as long as the code is not written prior to our morning coffee on a Monday, does not typically slip by us

As unbelievable as it sounds, it really does seem like you just have a couple of now non working fobs.

There is no way we know of to figure their codes out from the transmitted signal they produce, if indeed they are now even transmitting anything.

Sorry i can't help more

Roger
Glad the video also helped you

Hi Roger/Colin,

As I thought from the beginning It seems like I destroyed the 2 fobs because of the many failure attempts to program them with the previous firmwares.

Anyway(Just to be 100 precent sure) I will try them on my friend's car,
of course if there will be a suprise I will let you know.

Thank you very much for all the help I appreciate it.

Oren

Colin
Can you enlighten me as to what would cause the pump monitor line fault wiring wise?

Have been getting this fault coming up with Evo 1.02 and the new 1.03 but never had it in 1.00 and 1.01.

I did notice a readout somewhere in one of the SLABS functions where the monitor line voltage was reading 0.00v.
I'm wondering if this maybe one of the Amigo issues or if something's amiss in the software.
It doesn't come up initially, I think I may have put a brief description up in a D2 autobox thread, but it's a new one none the less.

Using Capitals, the difference between helping your Uncle Jack off a horse or helping your uncle jack off a horse...

Lovemyrangie, I also get this fault showing.
On v1.0 it showed up as right hand front abs sensor which I had confirmed as correct by the workshop yesterday. I now get the same pump line 1 fault that you mentioned, I think this is a fault with the programming in the updates to be honest.

Cheers,

Rob