Mark Posted September 22, 2010 Share Posted September 22, 2010 having acquired a programmable ECU for my TD5, I set about getting it to work on my truck using Rovacom. Fist job was to tell it to learn the immobiliser code - no problem, truck now runs on the new ECU. Second job was to set the injector codes to the same as my old ECU - Having got them out of the old one, I modified the new one to suit, but it would not write them to the ECU. Having tried his several times, I figured it was running ok without them, so I would have a go at remapping it. The remapping uses two files - the uprated fuel map and variant file, and the existing ones need to be backed up and erasred from the ECU first. Backup and Erase went fine. The Fuel map, transferred no problem. The Variant file started to transfer fine, but commuinateions seemed to fail about 3/4's of the way through the transfer. Since that point, I have not managed to get the ECU to talk to the Rovacom unit at all. I cannot interrogate the existing settings, erase the corrupted variant file or write new ones. As far as the Rovacom is concerned, it is not there.... Rovacom still happily talks to my existing ECU, so I don't think there is an issue with the interface. I am also powering the Rovacom from a transformer rather than from the vehicle, so battery voltage should not be the issue. So, does anyone know how to revive the ECU, or is it dead now? I find it hard to believe I can have killed it with a failed programming attempt... any help much appreciated. Thanks Mark Quote Link to comment Share on other sites More sharing options...
GBMUD Posted September 22, 2010 Share Posted September 22, 2010 This happened with Si's. Stick the battery on charge for a few hours then try again - it seems very sensitive to low voltage. IIRC there was a separate supply at one point... Chris Edited: Duh, only read half the post... Quote Link to comment Share on other sites More sharing options...
BogMonster Posted September 22, 2010 Share Posted September 22, 2010 Yes it can become a doorstop if it corrupted at a critical point in programming. I've never had it happen, but I know it can ... I think basically if you blat it at the point where it has finished erasing the old stuff and not yet finished writing the new stuff it no longer has enough sense left to talk to the computer and becomes an electronic vegetable. Maybe worth a chat with one of the ECU specialists they might have a trick up their sleeve? Quote Link to comment Share on other sites More sharing options...
RangeyRover Posted September 23, 2010 Share Posted September 23, 2010 having acquired a programmable ECU for my TD5, I set about getting it to work on my truck using Rovacom. Fist job was to tell it to learn the immobiliser code - no problem, truck now runs on the new ECU. Second job was to set the injector codes to the same as my old ECU - Having got them out of the old one, I modified the new one to suit, but it would not write them to the ECU. Having tried his several times, I figured it was running ok without them, so I would have a go at remapping it. The remapping uses two files - the uprated fuel map and variant file, and the existing ones need to be backed up and erasred from the ECU first. Backup and Erase went fine. The Fuel map, transferred no problem. The Variant file started to transfer fine, but commuinateions seemed to fail about 3/4's of the way through the transfer. Since that point, I have not managed to get the ECU to talk to the Rovacom unit at all. I cannot interrogate the existing settings, erase the corrupted variant file or write new ones. As far as the Rovacom is concerned, it is not there.... Rovacom still happily talks to my existing ECU, so I don't think there is an issue with the interface. I am also powering the Rovacom from a transformer rather than from the vehicle, so battery voltage should not be the issue. So, does anyone know how to revive the ECU, or is it dead now? I find it hard to believe I can have killed it with a failed programming attempt... any help much appreciated. Thanks Mark Is the Chip socketed? If it is, it could probably be read and reprogrammed. The alternative is to desolder the chip and reprogram it. All depending where the info is stored. If onchip, then resurrection is probably achievable. If the flash memory is on other chips then they can be desoldered and working ones put back in place. Either way, some work due. From my knowledge with other firmware applications, not Vehicle ECU's so may not be applicable, but I suspect it is.... RR Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.