TD5 ECU's

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?

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

Quote:

---

Originally Posted by 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

---

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.

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

Quote:

---

Originally Posted by Baben

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]

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

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.

Quote:

---

Originally Posted by OffTrack

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.

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 [bigwhistle])

Quote:

---

Originally Posted by Bert Def

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.