TD5 ECU's

**strangy** · 28th January 2019, 11:06 AM

Originally Posted by OffTrack

NNN500xx0 ECU's use a different high side driver chip to the one used in NNN000xx0 ECUs.
The two chips use different encoding of errors, which results in misreporting of the injector driver status if the incorrect version is used.
NNN500xx0 maps detect which driver chip being used based on the reported hardware ID, but the NNN000xx0 maps don't.

NNN500250 uses same the variant map as the NNN500020 so the hardware should be close to identical on both units.

If you want to try loading non-NNN500250 maps, use the ones for the NNN500020.

Hi,
Any chance you’ve moved into repairs on these things or can recommend someone who can in Oz?
My std NNN has opted to remain in overboost/fuel cutout, after a drive.
At least that’s the best thought/diagnosis I can ascertain.
Another ECU has me sorted but would like to fix it if possible.

**sierrafery** · 28th January 2019, 03:15 PM

Originally Posted by strangy

...
My std NNN has opted to remain in overboost/fuel cutout, after a drive.

Do you mean you can't erase that fault code from it?

**strangy** · 28th January 2019, 03:25 PM

Originally Posted by sierrafery

Do you mean you can't erase that fault code from it?

Correct and it remains in that fault condition.
As soon as ignition is on, the fuel pump and another relay constantly cycle on then off with associated instrument panel lights.
Engine runs then cuts out then runs again etc.
Nanocom shows overboost fault or fails to communicate.

**shack** · 28th January 2019, 04:59 PM

Originally Posted by strangy

Correct and it remains in that fault condition.
As soon as ignition is on, the fuel pump and another relay constantly cycle on then off with associated instrument panel lights.
Engine runs then cuts out then runs again etc.
Nanocom shows overboost fault or fails to communicate.

I doubt that it would be financially viable to chase that down, even on the labor side trying to diagnose which part is actually on the fritz, but I understand why you would like too.

Cheers James

**Bert Def** · 3rd February 2019, 06:23 AM

Originally Posted by sierrafery

Hi, i dont know exactly why the 500250 is cheaper maybe cos there are no standard Eu2 files made for it as for the others, you can see that in the attachment... though IMO being NNN and the latest version it should be fully remapable and i know i've seen few remapped of them even on Defender it's versatility being confirmed as advertised on this site https://www.cartechelectronics.com/r...stage-1-remap/ (disregarding the price of course

)

So NNN500250 is only usable for EU3 engines, with right corresponding map for defender/disco, thanks!

**Bert Def** · 3rd February 2019, 07:05 AM

Originally Posted by OffTrack

NNN500xx0 ECU's use a different high side driver chip to the one used in NNN000xx0 ECUs.
The two chips use different encoding of errors, which results in misreporting of the injector driver status if the incorrect version is used.
NNN500xx0 maps detect which driver chip being used based on the reported hardware ID, but the NNN000xx0 maps don't.

NNN500250 uses same the variant map as the NNN500020 so the hardware should be close to identical on both units.

If you want to try loading non-NNN500250 maps, use the ones for the NNN500020.

A good friend of mine has been driving around for more than a year with NNN500250 in his defender Post 2002 (EU3) without problems, he told me.
He also put the map on my NNN000120 (also def Eu3) last year and I checked it out with nanocom.
The program svloe005 svtnp006 comes from a NNN500020 (like you said!), and the 'config. tune' is the same as that from a NNN500250.
Now he wants to check what happened with a map of NNN000120 in his NNN500250.
I don't think it will work because there is no 'config. tune'

svtnp006

in a map from a NNN000120. Am I correct?

Thanks, Bert.

**Bert Def** · 6th February 2019, 07:17 AM

Hello Offtrack,

I'm a little confused now.

I know 4 men driving around in defenders Td5 pre 2002 (10p motor Eu2) with a map svloe005 svtnp006 in a NNN000120 ecu and they have no problems.

If a defender Td5 Eu2 drives well with that map svloe005 svtnp006 in a NNN000120 ecu, will he (she) also drive well with the same map in a NNN500250 in that defender Eu2?
Best regards, Bert.

**OffTrack** · 2nd March 2019, 05:20 PM

Originally Posted by Bert Def

Hello Offtrack,

I'm a little confused now.

I know 4 men driving around in defenders Td5 pre 2002 (10p motor Eu2) with a map svloe005 svtnp006 in a NNN000120 ecu and they have no problems.

If a defender Td5 Eu2 drives well with that map svloe005 svtnp006 in a NNN000120 ecu, will he (she) also drive well with the same map in a NNN500250 in that defender Eu2?
Best regards, Bert.

Hi Bert,

LR made tunes for both ECU variants after the NNN5000x0 was released so there are versions for both NNN000120 and NNN500020.
You know what the sum total of difference is? 2 bytes. One is the last digit of the variant name which can be either 5 or 6 and a checksum which changes by 1 depending on the variant. The checksum is probably irrelevant because it's never updated, even in remaps.

svloe005FM.jpg

The NNN500xx0 maps check which driver chip is being used.
The NNN0001x0 maps I've disassembled thus far don't - which is not to say they all don't.

So my advice - based on current information - is that NNN500xx0 maps will work on on NNN0001x0 ECUs. BUT it's a bit of a pointless exercise because the same base tunes exist for both revisions of the NNN.

And my advice - based on current information - would be only use NNN50020 maps if you want to try running something other than the stock D2 map on the NNN500250

If you want to run EU3 maps on EU2 engine that is up to you. It's not something I'm a fan of personally.

Strangy,

Sorry I don't do repairs.

Thread: TD5 ECU's

Thread Tools

TD5 ECU's

TD5 ECU's

Bookmarks

Bookmarks

Posting Permissions