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

    • Even more fun, leave all the ADAS stuff plugged in, but in different locations, hopefully avoid any codes!   And honestly, all these new cars with their weird electronics. Pull all the electronics out Duncan, and just shove an aftermarket ECU and if needed a trans controller in, along with a PDM. Make it run basic but race car styled!
    • To follow up a question from earlier too since I had the front bar off again (fking!) This is what is between the bumper and the drivers side wheel And this is the navigator side, only one thing but its a biggy! So basically....no putting coolers in the wheel arches without a lot of moving other stuff. Assuming I move to properly race prepping this car I'll take that job on and see how the computers respond to removing a whole bunch of ADAS modules
    • So I prepped the car for another track day on Wednesday (will be interesting to see coolant temps post flushing out and the larger reservoir, with a forecast of 3-14 being 20o cooler than last time I took it out). Couple of things to mention; since I am just driving the car and not taking a support vehicle, I took the rear seats out and just loaded the back up Team Trackday style. Look at all that space! To cover off removing the rear seat....it is weird (note the hybrid is probably different because it wouldn't have folding rear seats) Basically, you remove the lower seat base, very similar to a r series but it is a clip that pulls forward to release the base rather than it being bolted down. Easy Then, you need to remove the side section of the rear seat on each side. There is a 14mm head nut at the bottom of the side piece, the it slides upwards off a hook at the top to release; you also need to unhook the seatbelt from the loop at the top. Then the centre piece is weird. You need to release/fold the seats forward with the tab in the boot on each side From there, there are 2,x12mm headed bolts holding the rear of each seat to the folding bracket, under the trim between the rear seat and the boot (4x christmas tree clips there, they suck). The seat is out but you can see where the bolts attach to the bracket
    • As discussed in the previous post, the bushes in the 110 needed replacing. I took this opportunity to replace the castor bushes, the front lower control arm, lower the car and get the alignment dialled in with new tyres. I took it down to Alignment Motorsports on the GC to get this work done and also get more out of the Shockworks as I felt like I wasn't getting the full use out of them.  To cut a very long story short, it ended up being the case the passenger side castor arm wouldn't accept the brand new bush as the sleeve had worn badly enough to the point you could push the new bush in by hand and completely through. Trying a pair of TRD bushes didn't fix the issue either (I had originally gone with Hardrace bushes). We needed to urgently source another castor arm, and thankfully this was sourced and the guys at the shop worked on my car until 7pm on a Saturday to get everything done. The car rides a lot nicer now with the suspension dialled in properly. Lowered the car a little as well to suit the lower profile front tyres, and just bring the car down generally. Eternally thankful for the guys down at the shop to get the car sorted, we both pulled big favours from our contacts to get it done on the Saturday.  Also plugged in the new Stedi foglights into the S15, and even from a quick test in the garage I'm keen to see how they look out on the road. I had some concerns about the length of the LED body and whether it'd fit in the foglight housing but it's fine.  I've got a small window coming up next month where I'll likely get a little paint work done on the 110 to remove the rear wing, add a boot wing and roof wing, get the side skirt fixed up and colour match the little panel on the tail lights so that I can install some badges that I've kept in storage. I'm also tempted to put in a new pair of headlights on the 110.  Until then, here's some more pictures from Easter this year. 
    • I would put a fuel pressure gauge between the filter and the fuel rail, see if it's maintaining good fuel pressure at idle going up to the point when it stalls. Do you see any strange behavior in commanded fuel leading up to the point when it stalls? You might have to start going through the service manual and doing a long list of sensor tests if it's not the fuel system for whatever reason.
×
×
  • Create New...