TD5 ECU's

[joe.woods]

Been hunting around and cannot find a straight answer..Can a TD5 Manual ECU be programmed for an Automatic; I have an Auto and want to keep the original ECU as a spare; I have a big trip planned next year and I am collecting spares.

I have a Manual ECU NNN500250. I have bought a Stage 2 flash that I want to use. So can this be done or should I keep looking for an auto ECU. Cheers Joe

[Baben]

Hello Joe

With a Faultmate or similar, the NNN type ECU's can be programmed to any vehicle variant. Just last night I programmed a NNN500020 (manual D2 TD5) to an Auto.

That said, I have yet to see the NNN500250

[joe.woods]

I have a Nanocom will that do, if so how do I do it?

[Baben]

Does the nanocom works with the Vehicle Explorer software as my MSV2 does?

In other words, can you use the unit to reflash software into your ECU?

[OffTrack]

Does the nanocom works with the Vehicle Explorer software as my MSV2 does?

In other words, can you use the unit to reflash software into your ECU?

No it doesn't use Vehicle Explorer. The Nanocom works as a standalone unit and can reflash without external software.

[joe.woods]

Does this mean that the Nanocom cannot change the gearbox type on the ECU?

[Baben]

cool, then all you need to do is select the right set of 2 files based on your engine type (EU2 or EU3), vehicle type (D2/Def, man/auto)

[joe.woods]

So the ECU is out of a D2 TD5 Man, so the car type is correct how do I find or change the gearbox file?

[Baben]

If the nanocom works in the same way as the MSV2, you have no choice but to erase the ECU and program both the vehicle variant and fuel map files anyway

The files only work in pairs, one for the vehicle variant and one for the fuel map depending on market and emissions. If you program the ECU with an incompatible set of files it wont work, but you can erase and reprogram it again.

For instance if you have a 2002 EU3 engine, start with:

NNV001080 (swtnp004) NNS500170 (swdxr004)

please note - this is at your risk, sir! I can't take any responsibility for any consequences whatsoever

Do you have all the file info from nanocom?

[joe.woods]

I am currently at work so I will not be able to do this till Tuesday night.

My current ECU is NNN000130 - D2 TD5 auto
The 2nd ECU is NNN500250 - D2 TD5 Manual

I have a new map file from TD5 Inside Stage 2 and my original map file. I want to load the new file onto the NNN500250 and use it as my primary ECU and hold the original as a spare.

My understanding of what you say is that if I load the new map file onto the manual ECU the ECU will become auto.

Thanks I also understand that thinks go wrong and get broke ..Joe

[Baben]

Why not just use the nanocom to read the 2 files off your original ECU, and then program these into the new ECU? Then you don't have any guesswork

Not sure how this works in the nanocom, but with the MSV2 you can save both vehicle variant and fuel files onto the MSV2 unit, and then use them to reprogram the ECU (in case you make a snafu)

Apparently somewhere in the Vehicle Explorer software there is an option to read what files are loaded into the ECU, but I haven't found it :) - maybe you have this option in the nano?

[joe.woods]

I think the Nanocom only pulls off one file, I will need to look into this I don't know if it combines the files, I will do some more research but I feel like I am moving forward, thanks for your help:D:D I will keep in touch and let you know how I go. I sent you an email, Thanks again....Joe

[OffTrack]

Hello Joe

With a Faultmate or similar, the NNN type ECU's can be programmed to any vehicle variant. Just last night I programmed a NNN500020 (manual D2 TD5) to an Auto.

That said, I have yet to see the NNN500250

The programs will load but as I understand it there are internal differences between the manual and auto ECU's so not necessarily 100% compatible. You may also have trouble moving maps between ECU variants as the memory layout is not the same.

The biggest issue with the NNN500250 is that it was only ever fitted to D2 Manuals, so there only a D2 manual base map available. This lack of alternative factory maps is the primary reason the NNN500250 sells for substantially less than the other reflashable ECU's.

[Baben]

You are logically correct, but the only way to check for sure is to program it and see if it works. If it doesn't at least you can set it back to standard again and sell it

According to the the database, The fuel map and vehicle while variant I used on the 00020 shouldn't work, yet they did, except the cruise control won't work :) but I have a plan for that

[OffTrack]

The fuel map and vehicle while variant I used on the 00020 shouldn't work, yet they did, except the cruise control won't work :) but I have a plan for that

I'm sure I said something about "not 100% compatible". [bigwhistle]

[Baben]

I am not arguing with you or trying to prove how clever anyone is, just trying to help a feller out. Sarky bugger

[OffTrack]

Ok. Thought I better actually check the variant id on the NNN500250. It turns out that it actually uses the same variant id as some of the NNN500020 maps, so perhaps it isn't quite the orphan I understood it to be.

If you didn't mind having a backup ECU with non-functional cruise (and possibly other functionality) it might be worth trying out.

[Bert Def]

The biggest issue with the NNN500250 is that it was only ever fitted to D2 Manuals, so there only a D2 manual base map available. This lack of alternative factory maps is the primary reason the NNN500250 sells for substantially less than the other reflashable ECU's.




Hello, just pick up this topic again, because I'm interested.
I know that the NNN500250 is less expensive but why?
Why can't you just use a map from an NNN000120 in an NNN500250?
If you overwrite the base map svdxg003svtnp006 would that ECU still work properly also in a Defender or am I wrong?

Is there someone here who knows more about this please?
Thanks!

Bert.

[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/remapped-plug-play-engine-ecu-land-rover-discovery-defender-td5-nnn500250-stage-1-remap/ (disregarding the price of course [bigwhistle])

[OffTrack]

Hello, just pick up this topic again, because I'm interested.
I know that the NNN500250 is less expensive but why?
Why can't you just use a map from an NNN000120 in an NNN500250?
If you overwrite the base map svdxg003svtnp006 would that ECU still work properly also in a Defender or am I wrong?

Is there someone here who knows more about this please?
Thanks!

Bert.


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.

[strangy]

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]

...
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]

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]

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]

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/remapped-plug-play-engine-ecu-land-rover-discovery-defender-td5-nnn500250-stage-1-remap/ (disregarding the price of course [bigwhistle])
So NNN500250 is only usable for EU3 engines, with right corresponding map for defender/disco, thanks!

[Bert Def]

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]

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]

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.


148883

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.