1st Gen Haltech ECU Discussion

I agree with the statements on the cells above. Luckily at 8psi you won't be getting above the 160 row.

Speedy posted his "dialed" ignition map a few pages ago.


The injector comment reminded me I got the "injector duty over 80%" DTC the other week. Not sure what conditions did that

 

I never post the final anything Well except for sensor cals haha. But I do post breadcrumbs that someone could use to learn this stuff.

 

If you can swing it, I'd love to see some PC logs of what yours does on a hard pull or a dead stop to max speed pull. Either one would be neato to watch. I've gotten to 77% of my injector duty but not beyond that yet.

 

That would imply I can 1. Get my wastegate hoses to stay attached lol, and 2. Create a log (jk jk)

 

Oh come on, PC logs are the easy ones, hook up NSP and press F6 and just drive, it logs every sensor and map channel at once, then just press F6 when you're done. EZPZ

 

Huh, I didn't know it would log everything. Guess I'll try it once it's fixed (silicone hose kit coming beginning of next week). I seriously gotta do some heat management though, I found more damage from those graded pulls. My SCG-1s MAP sensor wire completely melted and dripped all over the exhaust manifold, and the gauge doesn't read anymore. Thinking a quick fix is to wrap the whole turbo assembly in some galvanized sheet metal like a burrito to keep it isolated from moving air

 

@Speedytech7 nailed it. Those circled zones are odd, they are too advanced in places and not advanced enough in places. You'd be fine most likely on pure e85, but pump gas is a bit sketchy there. Vacuum could use some tidying up, but it's likely not going to cause problems. And if you do continue running e85, I can't recommend a flex sensor enough, especially when you blend fuels just to give you that safety. The mix can vary quite a bit and could potentially cause harm.

 

Thanks guys, I appreciate the help. I do have my flex fuel sensor sitting in a box on my work bench. Just haven't quite gotten around to plumbing it into my return fuel line just yet.

I do have an adjustable rising rate FMU that I also haven't installed yet. Have thought about installing a fuel pressure sensor and trying it out with the FMU. Larger injectors is probably the better answer though.

On another note, I found some Haltech tunes in this thread to compare against. What do I need to do about this error when trying to open them?

 

Usually when it's missing the definition file it's because they removed that version because it had errors in it and they didn't want people putting the firmware back on that ECU. But sometimes it's just because your install of NSP is so fresh it hasn't reached out to pull down all the definitions yet. Make sure you're connected to the internet and then do the NSP update option and wait like 30 minutes

 

Hmmm... for some reason the update option is greyed out.

 

Also yeah avoid the FMU if you can, but having a fuel pressure sensor is always a good idea. I don't know what features TunerStudio and rusEFI have implemented for injector data and mapping but at the very least a fuel pressure sensor is a good diagnostic, if your ECU and software can do advanced injector definitions then you can have a very finely tuned low pulse width and good scaling with pressure fluctuation.

 

That's a pretty old tune if it was on 3.07 anyway, chances are it wasn't very nailed down. Try to find something 3.10 and up and be wary that everything you see posted in here is about sharing knowledge and experimenting and we're all always iterating and changing what we've done. A lot of the maps posted in here from a long time ago had too much timing and we've since discovered on the dyno with knock monitoring the 5VZ reaches MBT much lower and subsequently removed a lot of it.

 

I still seem to be getting the same error with a 3.11.3 that was uploaded by Trey a few months ago.

 

Never mind, I completely uninstalled the NSP software and reinstalled it, and that seems to have fixed it.

 

I'm always sussed out when I see Nexus updater and/or its AWS connections. Don't like it when software takes it upon itself to update without me knowing. Been screwed too many times when new features turn into new bugs

 

Turn off auto updates then, it's in the menu options. And don't forget to don the manual update hat too

 

Yeah, think I finally did that. My only laptop is a work laptop so that's another reason - don't need suspicious traffic on our IT logs.
I've been scarred into keeping old installers of applications I think may become paywalled, ad-ridden, or cloud based in the future. I'm the guy who doesn't buy anything networked unless I can run it locally. Cloud required? Account required? Only if it's free.

 

I inspect my outgoing traffic, Haltech is the least of my concerns in that dept

 

As far as I'm concerned, anything going to a jumbled AWS address is worth investigating. Usually it's telemetry data of some sort, which I crack down on at home at least

 

The piHole here strips a lot of things out for me. That and anywhere possible I use websites and unofficial apps for services