Originally Posted by BDC

When I tuned my buddy Lino Martinez' FC back in September time (using an E11v2 as well), we had spent several hours doing street and dyno stuff, basically getting it all sorted and doing well power-wise, but then I decided to update the firmware from Build 19 to Build 28 I believe it was. All the sudden, the car wouldn't start, was backfiring and popping, either running drastically richer or possibly not firing spark correctly. In any event, reverting back to Build 19 fixed the problem. The symptoms on Reese's car in alot of ways mimic Lino's symptoms so I've been scratching my head wondering whether or not something firmware related may be causing this. B

Originally Posted by enzo250

Don't try to fix what isn't broken!

Originally Posted by BDC

Regarding the massive flooding issue, one thing I'd done before heading back home to TX was to unplug the secondary injectors. Not to imply fault on Reese, but all options have to be considered as I was troubleshooting this; point in fact being the change-over from the stock 550 secondaries to Bosche 1680's:

1) With Mike's original map being untouched, if it were to ever use the secondaries at any point (which I believe it did prior to reaching 0Kpa), then it would instantaneously flood the motor at those loads, all else remaining equal
2) The re-wiring of the three new secondary injector clips may've been shorted at some point unbeknownced to me or elsewhere downstream on the stock wiring to Haltech wiring splicing for all we know, implying a previously unknown problem

The history of the engine and Haltech setup since Reese has had it has been sketchy at best. It hasn't reliable to any degree where we could use it as a benchmark to point back to and say to ourselves, "these are the changes recently made since it's last worked well -- let's go back to those and troubleshoot those one at a time until we find the culprit." That doesn't mean that the previous owner (Mike) did a bad job at all; it just means that it hasn't been up to the point of where it could be since Reese has owned it. In any event, that makes it difficult to work with as Reese could've very well inhereited unknown problems with either the wiring harness, the ECU itself, or who knows. The problem is mysteriously strange as it seems to fall outside the pale of "normal troubleshooting" where changes made by the tuner/builder would otherwise, normally yield positive results. For much of the time since it was installed, we've been banging our heads at the wall trying to figure out what's wrong. My gut has said "ECU-related" possibly being Firmware, hence the reasoning behind this thread's first post.

When I tuned my buddy Lino Martinez' FC back in September time (using an E11v2 as well), we had spent several hours doing street and dyno stuff, basically getting it all sorted and doing well power-wise, but then I decided to update the firmware from Build 19 to Build 28 I believe it was. All the sudden, the car wouldn't start, was backfiring and popping, either running drastically richer or possibly not firing spark correctly. In any event, reverting back to Build 19 fixed the problem. The symptoms on Reese's car in alot of ways mimic Lino's symptoms so I've been scratching my head wondering whether or not something firmware related may be causing this.

Other than some ignition changes per the GM LS-1 coils Reese is using, honestly the fuel and spark maps shouldn't be that much different from that of a street-ported 13B using the same 550/1680 combination. I've created several maps by hand throughout this past week either by using my older E6K maps as a template, using Lino's dyno and w/b tuned fuel and ignition map, or by using one of HITman's old E6S 20B maps. I've even gone back to him for help and tried one of his maps he'd custom-made for me a couple nights back. With the exception of the one night where we did manage to get about 10 miles on it as Reese mentioned, where we were promptly stranded for 2 hrs at a BP gas station in the freezing cold with both customers and the station clerk watching us, nothing has really worked. ATF has generally helped get it started, and on a rare occasion, it has seemed to run, throttle, idle, and even drive decently well. It's strange because the one map I custom made a few days ago seemed to start and run REALLY well, then all the sudden left us stranded and wouldn't re-start at all.

B