Thread: Nanocom Remap Gone WRONG! Help!

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

Originally Posted by Hamish71

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

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

Originally Posted by Tombie2

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?

Originally Posted by Tombie2

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.

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

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

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