Disco 2 Nanocom Faults - Strange One

OK, so many times I've checked the ECUfor any faults, only to find none showing on the Nanocom. I've even pressed clear faults numerous times as well. Tonight I've just been out for a hard drive, and before I set off, I checked for faults, as usual, only to find

(1,5) DRIVER DEMAND PROBLEM 1, (LOGGED LOW).

So I saved the fault as a text file on the Nanocom and went off for the drive to gather some data. When I get back and copy the text file on to my pooter, I find these in it

(1,5) DRIVER DEMAND PROBLEM 1, (LOGGED LOW).
(2,8) AMBIENT PRESSURE CIRCUIT, (LOGGED LOW).
(4,1) INLET AIR TEMPERATURE CIRCUIT, (LOGGED HIGH).
(4,3) COOLANT TEMPERATURE CIRCUIT, (LOGGED HIGH).
(10,1) AIR CONDITIONING FAN DRIVE OPEN LOAD, (LOGGED).
(10,2) FUEL PUMP DRIVE OPEN LOAD, (LOGGED).
(10,3) TACHOMETER DRIVE OPEN LOAD, (CURRENT).
(10,4) GEARBOX / ABS DRIVE OPEN LOAD, (LOGGED).
(10,5) AIR CONDITIONING CLUTCH DRIVE OPEN LOA D, (LOGGED).
(10,6) MIL LAMP DRIVE OPEN LOAD, (LOGGED).
(10,7) GLOWPLUG LAMP DRIVE OPEN LOAD, (LOGGED).
(10,8) GLOWPLUG RELAY DRIVE OPEN LOAD, (LOGGED).
(16,2) HIGH SPEED CRANK (LOGGED).
(21,4) DRIVER DEMAND 1 OUT OF RANGE (LOGGED).
(21,5) DRIVER DEMAND 2 OUT OF RANGE (LOGGED).
(21,6) PROBLEMS DETECTED WITH DRIVER DEMAND (LOGGED).
(22,1) ROAD SPEED MISSING, (LOGGED).
(31,5) INJECTOR 5 OPEN CIRCUIT DETECTED, (LOGGED).

So, after changing underwear, I've just been back out to double check for these faults, and with the Nanocom connected, it reports No Faults, so I saved the text file and this time it's empty. So, my question is, why would the Nanocom only show one fault, but when saved, a bucket load of the damn things seem to appear. I've never seen any of these before, in fact, until I got the Driver Demand fault tonight, the Nanocom has never shown ANY faults in the ECU at all.

Sounds like your Nanocom had a 'bad trip' . Know anyone else nearby with one so that you can compare back to back readings with?
Reflash the firmware? I had to do that with mine (twice!) when I got it as it wouldn't accept the unlock keys - not a good start.

Spong said:

Know anyone else nearby with one

Click to expand...

I can usually see the IoM from this area unless it's raining but I think it's a bit too deep to wade over otherwise you'd be welcome to try my Nanocom

Feathers McGraw said:

I can usually see the IoM from this area unless it's raining but I think it's a bit too deep to wade over otherwise you'd be welcome to try my Nanocom

Click to expand...

Try throwing it... I promise to catch it.

This has been on my mind since last night, and I'm worried now that the Nanocom isn't showing faults when it should be. I've even considered taking the car to a stealer and pay them 1 hours labour to put it on the Testbook and see what that says.

HI Shimmy,

Just in case, it was not an old file you opened and looked at was it?
Have you cleared faults and saved the file under a new name to see of it still contains them?

Cheers

I've never saved any faults codes before, so this was the first one. I've completely wiped the SD card, and cleared any / all faults from the ECU, been for a run, and no faults are showing on the ECU and even trying to save the faults to a text file, it reports that no faults exists, and the file it saves is completely empty.
I've posted the question on the Nanocom forum, but I've had no responses as yet. TBH, I've lost some faith in the Nanocom...

Do you have the latest version software saved?

Cheers

I'm sure I have, but let me check...

You did get a reply from Adrain on the forum.

Cheers

Yeah, just seen that after logging in. I thought I'd setup email alerts, but apparently not.

OK, so I've already got the latest firmware.

Kernel Firmware 1.10
Main Firmware 2.8
Graphic Controller Firmware 1.6Bn
OBD Firmware 1.04
Global Upgrade Level: 20170509

I'll re-flash it.

The firmware has been re-flashed with the latest version (forgot how long it took!). Checked the ECU for any faults generated on the run to/from work today, and the ECU has no faults, and saving the faults to a file has generated an empty file.
So, I'm going to have to put this problem down to "one of those things"... Not overly happy about that as I don't like problems that fix themselves.

There's nothing wrong with your nanacom. That's the best bit of kit ever.
But feel free to pay a main stealer for an hour of diagnostics where they use a system that's not a scratch on your nanocom.

With those list of thoughts I'd take a keen look at your injector loom for oil ingress.

I thought the Testbook system was superior to anything you could get for "home use"? Isn't that the reason why the main stealers use them?