1st Gen Haltech ECU Discussion

Spent an hour on the dyno with Gabe fine tuning the haltech with the new 1320 and the new 60mm pulley On a remote tune.
Was a good day with good results.
304HP-326TQ with a nice power graph

 

Ooo nice, roller dyno at altitude. Definitely good numbers to the wheels. How much boost was it making before and after pulley? How do you like the new SC vs original unit?

 

thats a really nice curve...

 

Looks like the 1320 is a much better supercharger than the original, cool.

 

I joined the club!

Anyone run an EGT sensor on the HT? it looks like it's another $450-500 for the CAN adapter and a sensor? Is it worth it?

 

I don't know of anyone running one. I'm not sure you could get to the level of power where it would be a useful tuning tool with the supercharger anyway. I suppose with that and per runner wideband O2 sensors you could do per cylinder injection corrections...

Welcome to the club

 

Thanks!

I ask because I put one in my stock downtube where the crossover comes in, it was for a Banks OBD2 I ran for a while off a Cummins I sold.

 

You're more involved in the Haltech forum stuff, so maybe you can provide some commentary:

I've had MAP prediction on at a high activation threshold just to watch it learn for a little while. What I don't get is why setting to a turbocharged engine we would want to cap it at 0psi but supercharged we do not. I've debated setting mine to supercharged since I'm fairly certain I would see phenomenons such as starting at 30% throttle at 2psi, transitioning to 70% throttle quickly, and it increasing a couple psi within the delay period (200ms by default). Maybe this would translate to a 3000rpm, 70% cell being 4psi instead of 0. And I can't see why this wouldn't be a benefit; I would assume not allowing this could lead to a lean condition actually. Right now the prediction table is expanding the default table to more 0s, and I expect it to continue for a while as it keeps learning. So what's the reasoning behind the cap, I wonder?

 

I wouldn't expect setting it on a high activation threshold to produce usable information I think you're mostly just fooling yourself there. But the reason supercharger gets it and turbocharger doesn't is because by the time a turbocharger has spooled even if it's a quick spool the transient event would have already decayed. The instant you're in the pedal hard with a supercharger there's boost so it needs to be able to counter that. The higher the RPM typically the less transient response that is needed if you're in heavy boost at low RPM maybe there's a benefit for you but I would check to see if you're going lean on a log first I wouldn't just assume that you are. I know you never liked this response but the way this part of EFI works is mostly a feel thing if it feels right it probably is. And I wouldn't want to add a ton of fuel to a map especially a turbocharged map that should already be adding a ton of fuel as soon as boost is seen. If you're constantly having a ton of transient events in boost which I almost never do by the way then that's stuff that's probably going to get trimmed.

 

Thanks

For the first part, I'm just referring to the derivative threshold (500%/s currently). The way it reads, it will adjust the MAP Prediction table and scale somehow based on this value, and continue to use the Transient tables when under this derivative. So flooring it will use the MAP Prediction. It's making changes that seem correct, so idk.

Well, I mean I feel like capping it is wrong so...lol. Guess I'll have to log and see if that feeling is wrong

 

If using MAP Prediction, isn't it referencing the fuel map? That's what I'm saying, I would think it should look at the 3k, 4PSI fuel number, not the 3k, 0PSI number. No extra fuel should be added than that with the new method, right?

But ya my driving frequently leaves me just hovering around -8inHg to -4inHg while cruising. Slow acceleration will put it at 0PSI, anything normal (30% throttle+) will usually be in boost by 3000. So really we're talking about moving from slow acceleration to "passing someone" acceleration or more.

 

Once you're in boost the regular fuel map should be able to handle the changes, remember transient is there to counter very fast changes from throttle opening that can't be measured directly the instant it is happening. On a turbo vehicle in boost that change, even if they're small turbos and spool very fast, isn't large enough/quick enough to merit a transient response vs a normal fuel map response whereas it is on SC vehicles. It happens very smoothly even with an aggressive boost curve. The only thing it could potentially help with is boost spikes from poor boost control, but that's slapping a band-aid on a much bigger issue.

But why not reset MAP prediction on your truck and enable it with it set to turbocharger and just try it, why overthink something you haven't observed yet? It learns very fast and even still it's initial guess from your fuel map should be close enough that you don't even notice what it's learning. If you feel stumbling from rapidly changing throttle position in boost then maybe adjust the MAP prediction map by hand a little and let it learn more. You can always help a learning map in haltech if you're not happy waiting.

 

So far the MAP has been good, but the only hiccup I've encountered is during cold starts. Once it starts and gets to idle, if I give it a blip of throttle it will stumble. It only does it like once or twice though right after the start and then behaves like normal. Assuming the values in the last two tables would be applicable since those are the only two with coolant temp as one of the axes.

 

Ever since this update I have been able to take fuel out of warm starts but my prviosuly bad cold starts are now perfect... Might need to add fuel to those on yours haha, the afterstart has a decay period that's what I changed.

 

So you mean you made the changes in the post start correction table in your case?

 

Yup, just a wee bit, how long is your decay rate though, might not make a difference if it is already really short.

 

What decay rate are you referring to? There is an enrich and disenrich decay rate setting in transient, but those are no longer applicable with MAP

 

Your post start map x-axis is time in seconds... unless you're increasing fuel over time (you shouldn't be) this is the time over which the post start added fueling will decay and your values set the rate based on temperature.

 

Ah got it. That's what you meant by decay.
Here's mine:
looking at it now, not sure what's going on in the upper range there. Probably a leftover byproduct of when I was having idle issues in the initial tuning stage. I need to mess around with this table some more to try and finetune things.

 

Ah yeah there it is, called it!




Looks like they contracted it out to AIM so it may not be as fully featured in IO and buttons as a IC7 tho