Thread: Nanocom help please - SLABS

Think its OK now computers 101 "turn it off and then turn it on again" All good faults read none logged.

Actually just about to post similar. Mine started playing up about a year ago and has got to the point of being a joke and unusable. Same thing keeps coming up as yours or unable to initialize or when it does start reading instruments just fails and shuts down after a couple of minutes, plus a few other error messages. Just about to fix it with a big hammer. Has turned into the most useless accessory in the Defender.

Originally Posted by rathgar

I'm trying to use my nanocom with the SLABS. But "when I try to scan faults is trys for a while and then says "communication error 1" then its says "unable to start communications with the ECU..." I have used its successfully for reading and clearing engine faults. I have triple checked the unlock codes unlock01 and unlock03 supplied and entered (case sensitive).

What am I doing wrong?

If it helps its for a Discovery 2 TD5

Hello,
Have you up graded to the latest firmware ?? mine did the same and the latest firmware fixed most of the usual things happening can't remember which one I think the 3.32 guessing at the number but all is good now
Ian

Access to any given ECU or function remains locked until an unlock code is correcty entered, Hence any unlock code proble results in a very specific "Function Locked" error message which is extensively documented and detailed on the Nanocom-diagnostics.com web site

"Communication error" messages are therefore exactly as stated, problems with commuications and completely unrelated to unlock codes.

Some older ECU's do require the Ign to be recycled between diagnostic communication events and some penickity ECU's such as the SLABS can sometimes be a little hit and miss.

Blackbox is constantly trying to improve this and impliment innovations in the Nanocom software to improve this.

Not long ago, BNS did indeed impliment such an innovation for the Slabs in a sequence of not jut retrying to estabish communications when it failed but subtly changing the timings with each re try that seems to have improved things significantly.

So it is indeed worth keeping oneself abreast of our changes and updates and keeping your Nanocom updated.