It's way more than me just saying "well hal said". I told you not only is the haltech pro tuner saying that's exactly what will fix it but it FIXED THE PROBLEM ON MY CAR. All the testing and tuning the world doesn't matter if that exact setting is what fixed the problem. So my "theory" is based on the fact that i had a problem and adjusting that fixed it. Going higher than that also created more problems too.

shortcomings would happen on more than 1 vehicle. The rest of us made small adjustments to our tunes and haven't had issues so it's obviously something that can be tuned out.

 

here's mine. more in line with Hal's specs

 

mx594, have you had the stock ECU reflashed for use with larger injectors?

 

I was using Osiris Tuner for a short period of time when I had the UTEC, but I reflashed it "back to stock" before I installed the Haltech.

So no.

 

You and I are not talking about the same problem. You are talking about the threshold causing problems with the cruise control, and you are 100% correct. If your threshold is too high (or too low apparently) the cruise does not work correctly. I am not disagreeing with you. But that is not what I am trying to fix. I know how to fix the cruise control - just lower the threshold and live with the popping sounds.

What I am trying to show is that there is no one threshold setting that will allow BOTH the cruise and decel cut to work properly. You get one or the other. I can either have a working cruise and a backfire on the decel transition, or I can have a smooth quiet decel transition and an effed up cruise control. And I have gone on to prove that the decel cut is indeed not working correctly when the threshold is low enough for the cruise to work correctly. Look at the datalogs. Do you agree that the decel cut is not working properly?

Read the above responses. The pops on decel DO happen on more than one vehicle. It seems that a lot of people have the pops with their Haltech, and they probably all have a really low threshold setting to get their cruise control to work.

 

i've never had a pop on decel from day one of installing my haltech. I can't even adjust settings enough to reproduce that problem so it's obviously in the tune. It's not a hardware problem with the haltech becaues it works on most vehicles and it can be fixed for most that have decel pop.

The last complaint you made was the cruise problem so that's what i was addressing. I'd rather have cruise control working properly then use fuel tables and targets to keep mine from making noise then lose my cruise to fix a fuel tuning issue. Just saying.

 

I FIXED IT!

Thanks to some sound advice from MR RIZK (Thank you!) I finally took the time to re-tune with higher latency numbers (I was waiting until I fixed my fuel resonance issues first, which are now fixed as well). Now I am using the numbers provided by Deatschwerks (1.35 ms @ 14v) which are a LOT higher than the numbers that Hal provided me with in my base map which I paid $100 for (.45 ms @ 14v).

This allowed me to lower the injection time threshold to .70 ms, so now the cruise control works flawlessly and there is NO POP on decel. It turns out I can have my cake and eat it too. It seems that the Haltech looks at "injection time" when determining fuel cut, which does NOT include the latency.

So let's say for example when the engine requires 2.0 ms injector pulsewidth. With my previous latency settings, the "injection time" would have been 2.0 - .45 = 1.55 ms. With my new latency numbers, the injection time is now 2.0 - 1.35 = .65 ms. This explains why I had to set the injection time threshold for decel cut so high before in order to get a clean cut without a backfire. What is still unclear to me is whether the haltech is looking at the stock injector pulsewith and then subtracting the haltech specified latency from that number, or if it is using the stock ecu's injection time at all...

This of course meant that I had to retune my entire fuel map - for example my VE at idle is now in the ~40% range whereas it was in the 90's before! This is more what you would expect from an engine at idle - I always thought it was a bit weird to have such high VE numbers at such low loads...it goes against the laws of physics! Take a look at my fuel curve now, compared to before. It looks like it's supposed to now - progressively increasing from low load to high load and from low rpm to high rpm.

 

no problems mate.. you are on a roll so keep up the progress

Now since you have it sorted time to change ECU's and start again for the next challange

 

That's good to know. Great job RIZK!