My new nanocom wont communicate with the ecu, it fires up and loads every thing, goes into the different areas like eas but has zero values and after a time (seems slow compared to my disco 2 td5 separate unit) comes up with the cannot communicate with ecu
any thoughts
cheers
blaze
For some ECU’s, the engine needs to be running to communicate with said ECU.
EAS is one of those.
On the other end of the scale, the BECM likes the engine to be switched off!
Cheers
Keithy
2002 P38 Range Rover HSE
Sequential LPG - Redarc Charger - TPMS - Ashcroft Locker
Wheel Carrier - Bullbar & Spotlights - 285/75/16 BFG KM3’s
On Board Solar - Stainless Snorkel - 2” Suspension Lift
update
so hooked it up at mates workshop and bingo, read with no problems on his (snapon) no problems reading ecu and clearing faults, now to try getting nanocom to reply to my messages
cheers
blaze
Blaze, I had exactly the same problem. I cleaned the OBD pins and plug several times, wiggle it, prop the plug up etc and it sometimes connects and sometimes doesn't. One thing that it needs is about a minute of ignition on time to be able to connect BEFORE I go into an application like EAS, HEVAC etc. If I go in too quickly it will not connect even if I keep trying. I have to go out to the screen showing the different ECUs then back in.
As others mentioned some ECUs like BCM, and I think ABS and maybe CC (all the ones important for safety) can only have one connection at any one time so need the engine off and once finished with one you need to cycle the ignition. Oh and I have to have the CC switch pushed in to get to the CC ECU, found that out after a lot of stuffing around.
Tip for Mr Nanocom, how about some on screen prompts to remind Users about these little things?
Search AULRO.com ONLY! |
Search All the Web! |
---|
|
|
Bookmarks