That basically fits with what I was told but they suggested that I send mine and they upgrade/swap and then when I put the 'new' ECU back in it needed to see the BCU and also have the injector codes reloaded.
Printable View
This is interesting... If you are sending your ecu away to be remapped, there is no reason at all why you would need to reload the injector codes and re-learn the security... Assuming your getting your old unit back!?!?
In a simplistic fashion the recipie follows along these lines...Take customers ecu, read existing map (to get that otherwise missing information), merge with modified ecu map, re-write to ecu. Test, tweak mapping & return to customer.
If someone is simply flashing a complete map onto an ecu then I can see where the problem lies. If thats the case, I wouldnt be sending mine there!
What I was told was that if it was my ECU that they put the new chip in then they would not guarantee it to work correctly unless they tested it which would mean it would lose the current mappings to my vehicle as they would not be able to test it in the vehicle where it needed to be to see the BCU. Following return to me it would need to put back in the vehicle and then have the injector codes loaded so that I could get up and running again.
From what you are saying I think they may be getting me to do the merging of the mappings.
There is an element of truth in what you have been told. In order to fully test they would need to put the ecu in another car and program it to that car, thus loosing your injector code and BCU/10AS settings.
However, there is also a fairly strong argument against testing, at least in another vehicle, not least because of the loss of settings, but also because no two TD5s are exactly the same - a map that is perfect on a test car, may smoke under load on another - that bit of smoke may be more than acceptable to you, but not the tester, or visa versa. It is therefore better if you are with the ecu when its been done to test yourself, but I appreciate the whole point of this thread is that this isnt possible.
A compatent ecu person should know what they are doing and have confidence in it, knowing that what theyve done will work. For the remaps that we do by post I always ask what the vehicle is for (competition / overland / everyday use etc etc) and they get a map accordingly.
You are not being asked to do any merging. You simply need to get the ecu to learn the 10AS/BCU settings (is it a Defender or Disco TD5??)
. I still cant figure out why they cant take the injector codes from your ecu before they start and put them back into your ecu before they send it back to you... Otherwise you need to take the rocker cover off to get to the numbers stamped on them...
If you do end up removing the rocker cover. Replace the rocker gasket when you put it back - once disturbed they have a habit of leaking down the back of the block (out of sight)!.
Jon,
Your correct, and its one of the reasons I dont do hard chipped TD5s at the moment..
I cant afford the extra for a de-secured ECU to send back and forth!
Plus no workshop at the moment (SteelX tell me its delayed in manufacture) so nowhere to set up my workbench :(
Common in Oz is exchange ECU's with "safe" mapping. Power increases are nice and strong, but not to the full potential of the engine.
I have around 40 maps now, including the reworked ones, but once the workshops up we're getting more intense.
I've also now got a power up for the new Defender and the TDV6 versions.
One time purchase, comes with programmer/deprogrammer that the owner keeps.
This allows them to return to stock for dealer visits should a warranty be required and then re-program it again once leaving...
They arent cheap, but they are Excellent performance gains...
They can then be moved on to the next vehicle with minimal cost when they upgrade.
Mike, how reliable is the security code learning option for the ECU in Rovacom? This was what I was going to do when Dale gets the ECU back.