1st Gen Haltech ECU Discussion

Backfired today around 12PSI too. Lambda (now that my gauges are up) was at 0.5. I'm starting to see why some vehicles run a MAP and MAF sensor. There's no way for it to know if I'm at 40% or 100% throttle at 12PSI. Mass is probably completely different

 

That don't sound right, what did you do to get what's essentially a 7.4AFR? People can tune boosted vehicles no problem on just MAP or even alpha-n (TPS), it's not the tuning solution, it's the tune. Why are you getting 12psi at partial throttle though? Why isn't your boost control scaling to demand?

 

Because I don't have TPS on a 4D axis?

 

I don't either, I'm actually a bit stumped as to how yours is demanding so much. When your throttle isn't open much. What's you minimum boost amount? Is it just unable to wrangle the two turbos with a single wastegate and creeping hardcore?

 

Have you tried calling Haltech Tech support?

 

I rather like the sounds of all of this

https://youtu.be/TGlNZeKPx-c?si=D_GAIV4AqkrLOYnN

 

@treyus30 I dunno if you saw these but the Haltech Support database now has a section for their CAN protocol specs, addresses, and formulas.

https://support.haltech.com/portal/en/kb/haltech/technical-library/haltech-can-protocol-information

 

It's doing what it's supposed to, it's just able to generate a lot of boost at low throttle. I could set the boost control on a TPS axis instead of an RPM axis since I basically have it asking for 16PSI the whole range of RPM so the axis is basically unused rn. But I don't have an issue with it generating the boost as long as it can handle it which makes me lean towards adding it elsewhere. 6PSI spring pressure, to answer that question

Well holy shit

 

I wouldn't even necessarily add a TPS axis, I'd probably just make a target boost pressure curve. Pretty easy to define and it makes it nice and repeatable.

 

Somebody today asked if I could make the module send inputs to the HT. I was like it's possible on my end, but idk if the HT can receive them and interpret them. He basically wants to send sensor data over CAN externally and have the Haltech read it in since there's not enough pins on the HT itself for NOS, traction control, and everything else he wants

 

There's already a bunch of IO extenders on the market, I'm sure you could do it, but is it worth it. Can you hit the same feature set (sensitivity and smoothing adjustment and delay) as the ones on the market. I don't think the haltech IO12 is a very good product but I think the CAN Checked MCE18 is hard to beat

https://www.vadpro.com/products/can...ltifunction Can,the flexible Can Bus protocol.

 

So I need the IO Expander CAN addressing added to those datasheet pages haha

 

I think it's coming, a lot of this has been added to the site recently, probably some Aussie intern typing it all up now ahead of the CAN feature set improvement launch.

 

Oh man, now I need to parse words down to individual bits for further processing it looks like.... aggh so much things to do so little time

 

How's this alter what you've been doing?

 

It looks like it adds the X:Y options where it's Byte:Bit to mean something, whereas before it was all 2 bytes together (Byte 1-Byte2), or 1 word (8 bits), was a single sensor data.
Basically I need to add handling & displaying boolean types now.

(sorry for all the edits, it's been over a month since I worked on it)

 

Looked through some of my logs when I was hard on the pedal... I somehow got 102% throttle position haha.

 

Probably just a tad off on the 100% voltage calibration point

 

Yeah must be, it's not doing anything up there anyway, pretty much only manages my transient. I have the old 4 wire TPS that has a separate circuit for idle too and I've been told it has a more condensed range of variability.

 

Popped a poll up just to take some stock and see if we are really ignoring something important