1st Gen Haltech ECU Discussion

I'd say your coils are healthy if that worked for ya. Still a pretty large gap, your initial gap was huge

 

I'm on IK24's @ 0.26 gap.

Haltech is running the show like a dream.

 

Rocking some IK22s at .30 here, probably have to tighten that up soon though.

 

Stock computer + AEM FIC struggled at Idle with the IK24's @ 0.26 (Random Misfires).

The Haltech doesn't care and it just putters along. Cruises just fine too. Pleasant surprises.

 

I take it you used the dwell settings from our tunes? Seems to work well and I haven't had any worried about hot coils

 

I think I understand async transient now.
Since your transient throttle derivative is only split-second (the rate you're moving your foot decays extremely quickly) (and barely even detectable without trace view on), you need async to add fuel to your other cylinders at the same time, otherwise sync will only grab a couple cylinder pulses before returning to normal fuel injection (thus skipping the transient enrichment for the sequentially pulsed cylinders), assuming your foot stays at the same TPS % after the initial transient event.

 

Slowly making progress on my tune, something went a little haywire at some point and I started running oddly lean, so I did a bit of work there.

But I'd like some gauges, so I started working on modifying the IC7 layouts for some personal touches. It reminds me of reskinning a video game haha

 

How are you porting over the fuel level? Do you have that wired into the HT?

 

You can wire it directly to the IC7 and tell it what the resistance sweep is

 

gotcha. That sounds relatively easy

 

So I put a few more hours into that attempt... still very frustrating. I was able to finally get a display SPI library to work after trial and error with the pin declarations, but no way of testing it because the circular display I bought I had connected to 5V logic level when it was 3.3V so I think I fried it.
So I tried a different SPI device (CAN controller) and library and something in it softlocks the Pico. Failed to debug because my C++ is very limited and it's not the easiest thing to find references across 5-6 libraries.

I'm pretty much defeated on this. Only thing left to do is go back to the tiny 0.96" OLED rectangle and work hard on memory optimization and program a smart way to update only digits that change to do fast refreshes. OR I could try writing 2 of my own SPI libraries from scratch - the deterrent there is it could be a tremendous waste of time if there's some kind of HW incompatibility I wouldn't find out until after the library is written and debugging begins.
Other option since people want bigger screens is I could see if there's enough room to add BTserial functionality, then anyone could just boot up a phone or tablet and have a custom display on that. Downside is the boot time and mountability. I really wanted to just get a screen I could 3D print into a gauge pod

 

So I could really use some help with these idle issues that I can't get rid of.
I've tried everything (Seemingly). Even my tuner couldn't figure it out.
The RPM's surge a lot at idle. Turning on the LT idle trimming helps a little, but when I turn it off it becomes really sensitive and will die if you're not careful. It typically shows up after it's been sitting at idle for a little bit like at a stop light and the engine bay is a bit heat soaked. It won't start surging immediately when you come to a stop.
Here's a video to best show the behavior.
It seems that it's surging because the AFR's fluctuate and that it can't quite seem to hit the target AFR at idle, but then gets worse as it tries to correct?


Video just uploaded so the full resolution might not be processed yet
https://www.youtube.com/watch?v=Uy8wZhHZb4U

 

If you followed my guide (looks like you might have from the RPM settings), that axis should be TARGET RPM, not RPM.

 

Show your post start correction tables.
Also, your electrical system voltage seems a little low.

 

Oh I guess I missed that. I'll change it to that and see if it helps

 

13.7V seems low? I have a voltage boosting fuse to up the charging volts and have the big 3 installed.

Here's post start correction

 

Ya your voltage is fine, good even

 

It should change everything lol. Before you were basically telling it the duty cycle to keep you at an arbitrary number, now it can correct to something.

Oh, and make sure your trim table has the same axis!

 

Ya that makes a lot more sense when I think about it lol

My trim table before was all over the place

 

it’s really hard to do that kind of thing without a real debugger, especially when unfamiliar libraries are giving trouble.

Could you use one board to do the data crunching and another to drive the display?