Jump to content
SAU Community

Recommended Posts

I though I'd keep this one to myself until yesterday when a resolution was reached and confirmed.

If anyone has an Elite 2500 I suggest you upgrade to the latest 2.34.00 firmware and ESP 2.42 software immediately, and preferably do it with your coilpacks unplugged or at least the coilpack power feed unplugged.

On the blue 2.8 Nitro 32 during a firmware update about six weeks ago I had a slight issue where during the update to my 2500, my coilpacks harness and main engine loom decided to smoke, catch fire and melt. Completely destroyed main harness along firewall and at coilpacks harness power supply plug. Car was running well before this and are using R35 coilpack upgrade from Godzilla motorsport.

Cause was unknown at this stage so ECU was sent back to Haltech for inspection and test, and ends up testing fine. After post mortem on engine loom discovered the earth wire which carries the coilpack power had melted due to excessive current, taking out the rest of the cables it was loomed with. After bringing this up with Haltech the only conclusion I could reach was that during the firmware update it triggered all six coilpacks to try and charge the primary side simultaneously for an extended period of time without discharging, which in turn will make an excessive amount of current flow through the power supply wires to the loom.

If you look at the coilpack 12v supply the positive is also much larger gauge than the ground wire. Compounding this is issue if you run R35 coilpacks which draw considerably more current than stock coils, if this is to happen the risk of cable failure is increased if all coils decide to charge all at once and then not discharge.

After bringing this to Haltechs attention they decided to retain my Elite for further testing, which confirmed that the coilpack outputs could indeed randomly turn on during the firmware update, as the ECU will be in a state of no configuration while erasing the existing firmware and writing the new one.

After receiving back my 2500, on the 21/10/2019 comes a new firmware 2.34.00 which the first changelog mentioned in it was the rectification of the coilpack outputs switching on during a firmware update.

Car was finally finished off yesterday with the original Elite 2500 on 2.34.00, and a whole new wiring specialties main engine and coil pack loom to replace the fried stock one. Fired up first go, no DTC's and all sensors reporting as normal.

Again, Please do update immediately with your coilpacks unplugged

 

  • Like 5
Link to comment
https://www.sau.com.au/forums/topic/479058-haltech-elite-2500-firmware-23400/
Share on other sites

Ouch. That sort of software "bug" is an absolute bastard to plan for in the hardware and software specification stage and in the programming/testing phase. There are so many possible random such things that could go wrong, it would be hard to imagine them all.

I guess Haltech could take a leaf from the designers of safety critical systems and just make sure that all outputs are off (assumed to be the safe state) at all times when not required - which would be especially true of those edge cases where the ECU program is not actually in charge, ie during flashing. Just needs one or two interlocks to be put in place.

It's surprising that they can fix it just with a firmware update though - so maybe they have already had the physical side of it in place in the original design, older firmwares were doing it properly and somewhere along the way the software side of it got lost or bugged out.

Thank you for that!

Haltech updates sometimes do extremely strange things, not long ago I upgraded the firmware and somehow after the upgrade all my I/O mappings vanished!

Luckily Haltech auto saves maps for you, so imported it back in.

They need to get Andy from Adaptronic (which is pretty much Haltech now) to allow Haltechs to be accessed without the need to be powered up. I remember with the old 440D Adaptronic you could just power it up with a USB and load/mod the map however you wanted it before you even connected it up.

Yeah it would be good to access the ECU while car is off, and ECU was USB powered. The new ESP 2.42 software, which was only released Monday 28/10 also won't upgrade from the old ESP. Have to completely uninstall 2.41 or earlier and fresh install 2.42 ESP. Doesn't erase any saved maps though as they are saved elsewhere.

There is also a bug in the ESP software on the knock control long term trim, which sometimes doesn't apply timing changes permanently to the base ignition map when applied.  Won't melt an engine loom though which was an absolute bastard of a job to replace.

  • Like 1
On 06/11/2019 at 7:50 PM, r32-25t said:

I just did mine, disconnected the igniter and main plug for the coil harness, no issue 

But did you enable rolling anti-lag? Need bang bangs on gear shift 

  • 1 year later...

Ok guys more heads up on Haltech firmware. If you are using 2.38.00 at the moment on an Elite 2500 or 2000 there is a problem with it - get off it now.

The problem is related to running the wideband, causing it to randomly malfunction and get stuck in boot mode. After speaking to Haltech the problem mostly occurs when upgrading to 2.38, but for me this happened when trying to move to 2.39 and the firmware update could not complete. This caused my Elite to lockup and get the wideband stuck in boot mode, which causes the wideband to draw max current.

Basically to fix it I had to go back from 2.38 to 2.37, then move to 2.39.01 which corrected the issue. If you're not on 2.38 don't worry as Haltech have since removed it from the firmware update list and is no longer obtainable.

There is also a new ESP pack 2.47.01 available too, which is not downloadable on their site. It is only installable though your existing ESP software when the ESP is using online connection.

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • Ah right. Maybe my rb just loves chewing through batteries lol.
    • On the R34 can't you just unplug the IACV? This is the way I've always done it on the R33. Disconnect IACV, get it idling around 650rpm, and then do a power reset on the ECU to get it to relearn idle (factory ECU).   The big reason no one has touched on as to why you'd want to get the base idle right, is that it means the computer needs to make smaller adjustments to get a good idle at 700-750rpm.   Also, cleaning the IACV won't normally make the car suddenly idle lower or higher. The main issue with the IACV gumming up is that the valve sticks. This means the inputs the ECU gives, aren't translating to changes in air flow. This can cause idle choppy ness as the ECU is now needing to give a lot of input to get movement, but then it moves too far, and then has to do the same in reverse, and it can mean the ECU can't catch stalls quickly either.
    • 12.8 for a great condition, fully charged battery. If the battery will only ever properly charge to about 12.2V, the battery is well worn, and will be dead soon. When I say properly charge, I mean disconnect it from the car, charge it to its max, and then put your multimeter on it, and see what it reads about an hour later. Dieing batteries will hold a higher "surface charge", but the minutest load, even from just a multimeter (which in the scheme of things is considered totally irrelevant, especially at this level) will be enough over an hour to make the surface charge disappear.   I spend wayyy too much time analysing battery voltages for customers when they whinge that our equipment (telematics device) is causing their battery to drain all the time. Nearly every case I can call it within about 2 months of when the battery will be completely dead. Our bigger customers don't even debate it with me any more ha ha ha. A battery at 12.4 to 12.6 I'd still be happy enough with. However, there's a lot of things that can cause a parasitic draw in a car, first of which is alarms and immobilisers. To start checking, put your multimeter into amps, (and then connect it properly) and measure your power draw with everything off. Typical car battery is about 40aH. Realistically, you'll get about half this before the car won't start. So a 100mA power drain will see you pretty much near unstartable in 8 days.
    • Car should sit at 12.2 or more, maybe 12.6 or 12.7 when fully charged and happy. If there is a decent enough parasitic load then it will certainly go lower than 12.2 with time. You can't beat physics.
    • Ok guess I can rule out the battery, probably even the starter and alternator (maybe) as well. I'm gonna clean those leads and see what happens if it's still shit I might take it to an auto electrician. Unless the immobiliser is that f**king heavy, but it shouldn't be.  If I start the car every day, starts up perfectly never an issue. Isn't 12v low, shouldn't it be around 12.5v?
×
×
  • Create New...