Thread: Nanocom EVO2 Vehicle Detection fail on D4 2010 - what am I doing wrong?

I made some progress and have been in contact with Nanocom, they are helpful but not able to resolve remotely.

So next step is I need a D4 (or D3 as backup, I also have the D3 unlock code) volunteer just to plug in my unit and see if the VIN is detected.
Process of elimination, is it my vehicle or the unit.

So all those D4 (or D3) owners around the East or South East of Melbourne, who would like a free fault code read and clear?

Step forward

Originally Posted by SuperMono

I made some progress and have been in contact with Nanocom, they are helpful but not able to resolve remotely.

So next step is I need a D4 (or D3 as backup, I also have the D3 unlock code) volunteer just to plug in my unit and see if the VIN is detected.
Process of elimination, is it my vehicle or the unit.

So all those D4 (or D3) owners around the East or South East of Melbourne, who would like a free fault code read and clear?

Step forward

Your other option is for a member nearby to try their Nanocom in your car.

Absolutely.
Looks like I have a D4 lined up to try, then depending on result might also go find another Nanocom with D4 unlock to try on mine.

With the kind assistance of Ritters I have found I get the same fault on another D4 (can't read VIN), so looks like the problem is with the unit not the vehicle.

If anyone around E or SE of Melbourne has a D4 enabled Nanocom and would assist in confirming the process of elimination by reading my D4 VIN that would be greatly appreciated.

Hiya SuperMono

First off, I would like to thank you for bringing this to our attention and for your patience and assistance with us in finding the cause and properly resolving it.

This is not the first time that members of this board have helped us fine tune the Nanocom BTW

Logically, as with almost any problem we have ever encountered, this would at first seem like either a simple Hardware or Software issue.

Initially we believed that this was a Hardware issue, because in the past despite having a vast number of same model customers we have had a couple of cases of this and actually although a different Body shape, my own Sport is electronically identical to a D4 using an 11 Bit CAN BUS. In these cases, the Nanocoms were returned and my sport was used to verify the problem in them.

The problem was immediately rectified when we replaced the CAN controller Chip which obviously led us to believe these chips were or had gone defective and it was therefore a hardware issue.

If you do get to find someone with a D4 Licenced Nanocom it will very likely work fine on your D4, leading you to the same Hardware issue conclusion.

However a factor that is quite unique to you and which we especially thank you for, is that unlike other cases, you also have a D3 that is licenced on the same Nanocom, on which you have no problems despite it using the same CAN controller chip !!!

I hope you can appreciate the dilemna this poses to us

Armed with this new insight, and with a passion for perfection my Tech team started digging very deeply into this a few days ago.
Fortunately we retained the Can Controller Chips we replaced on the other couple of cases to help.

We have already uncovered some startling things.

It seems that when we set filtering of CAN BUS messages in the CAN controller chip for just diagnostic traffic, in the case of 29 Bit for D3 or 11 Bit for D4, some of these chips take a few Milliseconds longer than others to apply the filtering for 11 Bit.

During this period, the Data Buffer is often being pre loaded with non diagnostic CAN BUS messages.

As I write, we are already implimenting a small delay that will overcome this in the software, however to go one step further we are also implimenting error handling and retrying in the event the Data buffer contains non diagnostic messages.

I have been promised a software solution by early next week, which we will be forwarding to you for your own final field testing that I am very sure will resolve this problem.

Obviously we are very sad that you had this problem, and can but only apologize and hope that you can appreciate that at these levels of technology, even with the best effort and intent, these things can happen.

All we can do is try to figure out the problem and rectify it ASAP.

ATB

Colin

Thanks Colin, as I mentioned to Chris via email, all cool this end and no problem waiting for the code cutters to do their thing with 0s and 1s.

FYI for anyone reading I contacted Blackbox after I tried the unit on the other D4 and they immediately responded with a positive effort to try and resolve the issue.

I did wonder about resetting the unit and removing the D3 unlock code just to see what happened. Sometimes you have to do all of the little things in all of the combinations just to understand what's happening.

Thanks SuperMono

I have been promised a software solution by early next week, which we will be forwarding to you for your own final field testing that I am very sure will resolve this problem.

Although a little more Mid than Early into this week than I would have liked, nonetheless my Binary artists have been very hard at it and have produced a solution that should fix this little problem that you can now test, and have been sent the details.

Once again many thanks for your patience, understanding and assistance in this.

ATB

Colin