 | Home > Puma (Tdci) > NANOCOM issue - too many fault data to process |
 
|
|
|
| hornet Member Since: 04 Jan 2010 Location: Western Europe Posts: 361  |
Which Version do you have? Maybe an upgrade helps...
New BBS V1.34 Firmware upgrade February 13, 2018 BBS Firmware Version 1.34 is now available in your Restricted area: www.nanocom-diagnostics.com/restricted Kernel Firmware 1.10 Main Firmware 2.8 Graphic Controller Firmware 1.6Bn OBD Firmware 1.04 Global Upgrade Level: 20180212 Changes incorporated in this release: Vehicle specific: Disco 2 BCU Ododmeter Sync fix Defender PUMA Engine Management Fault code reading fix P38 Gems Instrument Mode capture fix This firmware update contains memory handling fixes for improved speed and stability. Edit: Latest Version is 1.37 or 1.38 beta |
||
16th May 2024 1:04pm |
|
| diesel_jim Member Since: 13 Oct 2008 Location: hiding Posts: 6093  
|
To be honest that could be a factory fresh LR product
 |
||
|
16th May 2024 6:50pm |
|
| MadTom Member Since: 10 Sep 2013 Location: Olomouc Posts: 625  
|
Ask for help on Nanocom forum.
What fault reading did you try to use? There are multiple options and some results in this. "Drobek" = The Small One - Discovery 2, "Blufínek" = The Blue Thing - Defender 130, and for me at least Ford Mondeo  |
||
|
17th May 2024 7:24am |
|
| Bradders130 Member Since: 27 Nov 2021 Location: Southampton Posts: 83 
|
Hey Djvanas, I know that this is a while back now, but did you ever get this one solved? I have the same issue.
|
||
|
30th Sep 2024 5:36pm |
|
| djvanas Member Since: 30 Oct 2021 Location: ‘s-Hertogenbosch Posts: 18  
|
Hi! No never been able to fix it 🫣
|
||
|
30th Sep 2024 5:38pm |
|
| Bradders130 Member Since: 27 Nov 2021 Location: Southampton Posts: 83
|
Thanks...I hear you. I just tried updating mine and still get the same result.
I’m going to try getting in touch with Nanocom and see what they say. I’ll get back to you if I find a solution |
||
|
30th Sep 2024 7:45pm |
|
| Bradders130 Member Since: 27 Nov 2021 Location: Southampton Posts: 83
|
Hi Djvanas,
The Nanocom formum mod guy got back to me and here is his answer. A bit technical in one sense, but I think the long and short of it is, don’t worry about it. So the message I sent is as follows, "I know that this subject has been covered before, but it is not resolved... So when I connect my nanocom to my 2012 Puma Defender and select the fault codes "read - not tested” I get..., "FAULT CODES - READ NOT TESTED Too much fault data to process. Please consult the user manual for further information.” The user manual is of no use at all as the issue is not mentioned - unless I’ve missed it, and nobody seems to know what the problem is. It seems to be mentioned on defender2.net, but was not revolved. I have done a search here and the only reference I could find was from 2014 and apparently “Nanocom" was going to be looking into it… but it appears the problem continues. I have just updated my Nanocom to the latest firmware, software etc and it’s still doing it. Does anyone know what this problem is or how I can solve it please." The reply is as follows, "Hello, we explained multimple times over the years what is a TESTED and NON TESTED fault code, you only need to read the TESTED faults, if you want to read the NON TESTED faults you will need to do it on 1 ECU at times. Tested fault codes [DTC]: This function is like the traditional fault code memory in that any faults shown here have been tested and have failed. Not tested fault codes [NTDTC]: One of the status bits in this status byte that is allocated to each possible code is a test state bit. This bit defines if the self diagnostic test associated with, or that would cause a particular code to be logged, has been performed by the vehicle system control unit or not, since the last time the fault memory was cleared. This feature actually means that after clearing the fault code memory, every single possible fault code that could be stored by each ECU is in fact stored right from the beginning but with a associated status of being a not tested Diagnostic Trouble code [NTDTC]. This means That the ECU did not fail the test that cause the fault code to be logged, but then it did not pass any test either, in essence it does not yet know if there is a problem in that circuit or not. Many of these NTDTC's will disappear almost straight away, when the system is first used or the ignition turned on, because most of the tests associated with these NTDTC's require no particularly special criteria to be met and therefore occur immediately, and they will pass. However, some tests may require the vehicle to be driven or warmed up, or put under a particular load or other input circumstances met, before the conditions for running some of the tests are valid. Of course any test which runs and then fails, leaves the fault listed but changes its status from NTDTC to DTC [DTC], meaning it is showing a problem. Regards, Alex” Complicated answer if you ask me, but hey... |
||
|
3rd Oct 2024 4:43pm |
|
|
|
| All times are GMT |
< Previous Topic | Next Topic > |
Posting Rules
|
Site Copyright © 2006-2024 Futuranet Ltd & Martin Lewis
