Nanocom Remap Gone WRONG! Help!

[Hamish71]

Was doing a remap on a D2 2004 TD5 Today. It got all the way through to the end...almost. Then said it had an error, and to try again. Now, Nanocom will not communicate with the ECU.

Error when trying to map says cant communicate with "map loader".
Error when trying to read settings/faults or anything else is cant communicate with the ecu.

All other electrics work. Car turns over, but will not fire.

Cant go back to stock map because of communication error.

Any ideas? Is there a way to "reset the ecu", or, is it as I fear, that the ecu has been partly re-written and is now useless.

[Tombie]

Airbag it to me tomorrow... I will look at it...

In the meantime.. Check your battery voltage... Bad writes are often the relm of low voltage.

If possible, I will write a stock map onto it (no charge) and send it back to you..

I have a couple of days off and I am determined to catch up on the mountain of PMs, Emails and jobs to be finished...

[Tombie]

Any ideas? Is there a way to "reset the ecu", or, is it as I fear, that the ecu has been partly re-written and is now useless.

These can be fixed...

[Tombie]

If you have had a custom map written for your vehicle, to prevent mystery fault codes you'll need an ECU of the same suffix as the one the map was written for.

So if your map was coded for NNN500030 then you need NNN500030
If it was for NNN500130 then NNN500130 etc. etc..

If you have yet to get map written, then any NNN to suit your vehicle type will work..

BUT there are rules!!!

NNNxxxx20 - Defender / Disco Manual
NNNxxxx30 - Discovery Auto

[Hamish71]

Airbag it to me tomorrow... I will look at it...

In the meantime.. Check your battery voltage... Bad writes are often the relm of low voltage.

If possible, I will write a stock map onto it (no charge) and send it back to you..

I have a couple of days off and I am determined to catch up on the mountain of PMs, Emails and jobs to be finished...

Address?

[Hamish71]

If you have had a custom map written for your vehicle, to prevent mystery fault codes you'll need an ECU of the same suffix as the one the map was written for.

So if your map was coded for NNN500030 then you need NNN500030
If it was for NNN500130 then NNN500130 etc. etc..

If you have yet to get map written, then any NNN to suit your vehicle type will work..

BUT there are rules!!!

NNNxxxx20 - Defender / Disco Manual
NNNxxxx30 - Discovery Auto

Thanks Mike, this is for a friends vehicle, a 2004 TD5 Auto. Will send you the ecu, if you give me an address?

Perhaps text it to me...will pm you my number.

[TOUTERRAIN]

I had same error on an auto, I had M and S lights in dash as well, I got round it by re writing map in 'defender', ( mine is nanocom Evo ) once I re wrote std map I used def to re write tuned map.
No further problem,
Anthony

[pohm66]

Seem to have the same problem when trying to install a td5inside map onto a NNN000130 ecu

The map failed to load and now I get the M, S, HDC and off road lights on the dash.

The Nanocom Evo can no longer interface with the ECU no matter which ignition position I have.

The Evo can access the ACE and valeco Ecus OK.

Checked the voltage after reading this post.... 12.3volts.

Any ideas?????

Thanks.....

[pohm66]

I should note that Kelvin at td5inside has been assisting me greatly with this and as I'm using a Nanacom Evo the write process is different to the previous version.

Anyway looks like we have an understanding of the issue at hand..... The moral of the story is "DON'T CHANGE THE MAP FILE NAME":(:(:(.

I thought the security was embedded into the mapfile not also in the file name. Kelvin has enligtened me on this.

I changed the name to track the map versions for the 2 ECUs I have and have now clobbered the ECU / Map security....bugger. The tell tale signs are the symptoms in my previous post.

Cheers....

[disco_thrasher]

Yeah we are going to reboot the ecu and send it back to you with the remap loaded up for you

regards kelvin

[TOUTERRAIN]

Hi All, I too have had a problem with the EVO,:mad: but managed to cure it, :D
The problem seams to be 2 fold, one the onscreen instructions are a translation from italian, 2 the timing is critical

Power up the evolution by pluging in EOBD port, DO NOT TURN IGNITION ON at this stage

Go into TD5 Map

Follow prompts i.e. do you want to write this file to ecu ect,
Then every time you do something count to 5 click OK,
Count to 5 again,
when it asks to wait 15 Seconds, wait 20/25,

I had a half day with this, I read ECU went to save Std file and was told not possible, after that all I got was unable to communicate with ecu,
This was a friends defender, so I took late ecu of my disco, and fried that,eventually I cracked it,I took my time and did as above it has been perfect every time since
Hope this helps
Anthony

[Benny_IIA]

..............................

[Urban Panzer]

If you have had a custom map written for your vehicle, to prevent mystery fault codes you'll need an ECU of the same suffix as the one the map was written for.

So if your map was coded for NNN500030 then you need NNN500030
If it was for NNN500130 then NNN500130 etc. etc..

If you have yet to get map written, then any NNN to suit your vehicle type will work..

BUT there are rules!!!

NNNxxxx20 - Defender / Disco Manual
NNNxxxx30 - Discovery Auto

Hi Tombie,

will be sending a pm bud.