Thread: Great disappointment with a new Nanocom Evo

BBS Guy,

Have been playing on the car this morning for a couple of hours following your instructions re bad earth.

There is no didfference to the fault.

Just to summarise, I can access ALL areas with the Nanocom with the engine off, however, when the engine is on and I access say fueling inputs I get a dialog box that says working. Then after a second or so the data flow starts to populate the boxes, then after about 2 seconds later I get a message stating that communication with the ecu has failed. This happens with "TD5inst.APP" loaded on start up or from the TD5 engine menu in normal mode. I get the same message scenario for the abs module too.

Regards,
Ray

"This happens with "TD5inst.APP" loaded on start up or from the TD5 engine menu in normal mode. I get the same message scenario for the abs module too."

My mistake, it works fine in instrument mode! Sorry. Just faults in normal mode.

Hiya foz.in oz

Glad to hear your instrument mode works as expected.

Do you still have the same engine running problem in ABS without moving the vehicle?

Hey BBS Guy,

Just done some testing in the back yard with the Evo.

In the WABCO app I can read all the functions with the engine running and the car stationary. If I move the car, I can maintain comms AS LONG as I stay below the speed that the ABS dash lights goes off! As soon as I exceed that speed (~6-8pmh) I get an error that states "Cannot perform that function" then after a second the cannont communicate with the ecu meassage appears. I have to turn off the ignition and wait for 15 seconds or so before I can reconnect the EVO and ecu.

Hope this helps.

Regards,
Ray

Hiya foz.in.oz

Thanks for taking the time and trouble to test and confirm my suspicions.

I know some ABS ECU's simply do not support diagnostic communications when all four wheels reach above a few KPH, 7 IIRC.

It's just i can't remember which ones

Well it was a very long time ago when we first covered all this with our equipment and i have since worked with quite a lot of different systems and later technologies.

I know what you are probably thinking, why have dynamic wheel speed values at all if you cannot access them when moving?
Well i recall the OEM (TestBook) tests were all about jacking wheels up and rotating them by hand to test each wheel speed sensors input.

Frankly a slow crawl keeping to just a few KM would test all 4 at once much easier and faster, but then the TestBook did not have it's software written to allow this, was not that portable and was / is all about wasting time a dealer could charge to the customer

Just one of the many reasons we do what we do and much better IMHO

Also i recall some ABS ECU's do need to have the Ign reset before you can re establish communications and worse still they then Block communications to other ECU's too. So on a P38 for example, if you read fault codes from the ABS and then want to do so from the EMS you can't until you reset the Ign.

In the hope of saving as many members / readers as possible from getting into trouble, as we do seem to have a growing number of customers who have managed to end up with what is obviously a corrupted firmware flash drive, including farmergeo, might i re iterate and re emphasize my earlier comment.

the TD5 ECU occasionally fails to respond to a request for live data when the engine is running. Sadly in a few cases, folks who think it's their Vehicle, their Nanocom unit, their OBD connection or otherwise have tried all manner of things, which sadly can under just the wrong circumstances, can corrupt the units firmware flash drive or have other un desired effects.

We have already made changes to solve this TD5 ECU with engine running problem as well as making the firmware flash drive write protected at all times, except during updating etc and even improved the restore function for the drive significantly as some have had problems doing this.

This is currently being Beta tested, so we really are on the case with this and doing the best we can to resolve it as quickly as possible.

So if you do get a loss of communications during live Data sessions with the TD5 ECU, it is best to stop trying until we release a software upgrade to fix this.

Sadly it seems like there is also a problem with using the restore function, in that it only seems to work when the unit itself is used to save a restore file and not when one we supply is put on the SD card.

So if you use the unit to save a restore file to a card and then get a corrupted firmware flash drive, you can use this card and the restore function to fix it.

Our Beta testers do report that applying an update does fix a corrupted firmware flash drive, but sadly as we are closed for re location it will be at least 2 weeks before we can generally release the first upgrade package which will of course also fix all these problems

Hi Colin,
I hope the move went smoothly for you. Are you back online for business again yet? If not can you please provide an estimate on when it will be.

Thanks.