I hear ya.. But at the end of the day it is a base map. Base map should get the car started and all functions to work. Does not mean it is anywhere close to the tune you are after.

 

So in the decel cut settings there is an ignition retard setting. I have tried 0 and 2 degrees and it doesn't seem to make much difference. Is this supposed to be the ignition value in BTDC that the timing will go to during decel, or is it just the amount of retard that will be applied to the base timing values? Because when I datalog the ignition timing during a decel event, the timing is in the 30's. I am using copy through timing for all vacuum rows. Does the ignition retard still apply when using copy-through? I wish Haltech had more detailed descriptions of these functions, because I really have no idea what exactly this setting does (or is supposed to do).

I am pretty sure my decel cut isn't working. The injection time never goes to 0. The lowest it goes is about ~1.3 ms even after my TPS goes below 2% and after the .5 second delay.

 

mx594, I assume you are logging "Injection time". Take this as a grain of salt but I was once told this value is no what the injecter is doing but what the haltech is seeing from the OEM ecu. Someone
correct me if im wrong.

On my data logs on decel I do not see the injection time go to 0. Best I see is 0.800ms @ 0.1% TPS while decel is 1

 

That is correct, I am logging "injection time". I was under the impression that this value was the actual injection time being used, including the added injector latency.

In either case, if the lowest I see is ~1.40 ms then that would explain why my decel cut seems to work with a injection threshold of 1.50 ms but not with a threshold of .80 ms.

 

Does anyone know -

In the transient throttle percentage enrichment table, if there are positive values for negative delta load, does that mean it is adding fuel or taking away fuel (like a disenrichment?). Books that I have read say that a certain amount of disenrichment is needed when the throttle is closing (negative delta load) to prevent a rich condition.

In the base map that Hal sent me, it has a 100% value at -5% delta load and 50% at -2.5% delta load (see screenshot).

The reason I ask is because it will not let you put negative numbers in, so as far as I can tell you can’t have a transient throttle disenrichment.

 

I love this picture....perfect in so many ways.

 

LOL, care to take a crack at any of my above questions?

 

in the manual it has a section on how to do the transient throttle and delta load. Mine is setup just like yours but just different delta t numbers since they are dependant on each individual car.

 

I am still getting some loud pops on decel. I don't dare rev match on downshifts anymore, because it pops loudly every time. It's somewhat embarrassing. I miss the stock ECU

 

I get pops on decel with stock ECU / Uprev but it isn't that annoying because I don't have a stupid loud exhaust. At least you can adjust the decel and disenrichment tables with your Haltech... stock ECU has no such tunable variables and you'd be far worse off with your large injectors even when 'scaled' via Uprev.

 

i was messing with my car the other day adjusting some things and noticed when i had my full vac (far left) settings too rich it was starting to pop a little on decel. When i'm on decel i have that target A/f set to 16:1 so it will run 16:1 before the fuel cut comes in. With that i haven't had any pop.

make sure you log to see how far to the left your tracer goes on decel and make that column 16:1.

 

That's weird, when I was using Osiris and 600cc injectors it never popped like it does now.

 

I have been driving around for a few days now with the decel cut injection time set to 2.500 ms. I haven't heard a single pop. Not even when rev matching. It drives soooo much nicer this way! I am probably going to leave it like this for now, because I would rather have clean and quiet decel transition than functional cruise control.

Why can't the Haltech use actual throttle position for decel cut, instead of accelerator pedal position? That way the cruise would still work. Or why can't the Haltech recognize when the cruise is engaged and prevent decel cut?

 

Yep I never understood that in the basemap either. So I changed it to enrichment only.

I have very mild pops on decel - if the AFR is lean in your cruise columns, you can reduce the popping without touching the decel settings.

 

are you talking about delay til fuel cut? mine is set to 0.70ms. 2.5ms seems really high. It was 0.55ms stock and that caused problems with mycruise but when i raised it to .7 it was fine.

Decel cut shows in the haltech as TPS initiated. It doesn't use Accel pedal, it cuts based on the Throttle position sensor that is on the main menu under advanced options as "throttle value".

 

2.5 ms IS really high. That's my point. If it is set too high (above ~.85 ms) the cruise won't work. I have never heard of the cruise having problems if this is too low...I'm not sure what you are talking about. The Haltech basemap has this parameter set to 2.5 ms. So with the base map provided by Haltech, the cruise won't work.

At 2.5 ms there are no pops, no burbles, just clean quiet decel. Just like stock.

I'm pretty sure the Haltech uses the APP for fuel cut. Otherwise we wouldn't have the problem of going into fuel cut when using the cruise control. When you engage the cruise and take your foot of the gas, APP goes to 0% but I really doubt the TPS goes below 2%.

And I STILL don't see the injection time going to 0 during decel cut. It only goes down to about ~1.2 ms. Are you guys sure it is supposed to go completely to zero?

 

binder was talking about seconds and you are talking about milliseconds. I think.

 

No.

 

My Haltech makes my car pop too, love it

quick push on acc and release makes a nice pop pop WOT up to a bit over 4.5k and release pop pop pop

 

To each his own I guess. To me it just sounds like a crappy running, poorly tuned car.