That's it! I'm effing done with this ECU! Going to megasquirt!

**Turbo Nasty** · 10-13-2017

Originally Posted by steveo

how do you mean? lets see your bin, xdf, and target offset data

I mean it's hot as hell in Arizona and that's the last time I tuned the car and it's stayed hot until recently and now my tune is way off. My tune was never really too good to begin with.

I did just have success richening it up. I got a wide open throttle run in an it was pig rich all the way! I did this by setting the 'Open Loop % Change AFR vs Temp' to all zeroes, and 'Open Loop % Change vs MAP' to all zeroes. The one that made the big difference was 'MAT Compensation Counts vs MAT' set to all zeroes. after the very rich WOT run I adjusted the affected temperature ranges to 40 down from the factory 128. it got my idle around 13.5 AFR and full throttle the same.

**Turbo Nasty** · 10-13-2017

Why so many crazy variables on this car!? I'm tempted to set everything to zero and just run off of the fuel map alone and retune the map for it The only noticeably affective variable was the 'MAT compensation Counts vs MAT'

**Turbo Nasty** · 10-13-2017

Here's todays bin.

**Turbo Nasty** · 10-13-2017

I'm using the $8D-1227730-V1.xdf.php

for some reason I was not allowed to upload it here. it said it was an invalid file.

**steveo** · 10-13-2017

Originally Posted by Turbo Nasty

Why so many crazy variables on this car!? I'm tempted to set everything to zero and just run off of the fuel map alone and retune the map for it The only noticeably affective variable was the 'MAT compensation Counts vs MAT'

this isn't at all normal, there are no 'crazy variables'. 8D is supposed to be really easy to tune, with a VE table in the ballpark, it should be drivable in all conditions. i tuned an 8D car for a guy once and had no problems, in fact on the stock bin it ran alright, just sucked a lot of fuel.

i know it's frustrating but do you want to try starting from scratch?

i looked at your bin and i think your VE tables are probably awful. i also saw a few tables for fuel compensation vs temperature and map were zeroed out. i think those are best left alone.

with your trouble with injector offsets, show me the injector data you're trying to enter and lets figure out why it wont take it. it should accept anything from zero to 7782 usec. just focus on getting the ~9-14v values correct, if you're outside that range, you're limping home anyway. i wonder if you're trying to put msec values in there or something.

**steveo** · 10-13-2017

i looked at your bin and i think your VE tables are probably awful.

i'd like to clarify that statement and just say that after tuning speed density for a while, you get to look at a ve table and go 'that shit will never work'. and that's exactly what pops into my head when i see yours.

was this developed from wideband data, trims, by feel, or what?

**steveo** · 10-13-2017

also how about a datalog and an adx? i want to troll it for sketchy sensor output.

if the forum wont accept a file simply zip the thing or rename it to .bin and tell us what the old extension was.

**steveo** · 10-13-2017

maybe this will give you some hope

i put a DGV weber carb on my beater mazda truck. it's pretty stock except for some crazy handmade exhaust.

it's a mechanical progressive carb, that means one barrel opens until half throttle, then the bigger barrel opens till wot, so a quiet and efficient cruising range with a massive (and fairly sudden) boost for heavy throttle.

with the jets that the mfr swore would run fine, it ran great on primary barrel, but when the secondaries open, it would bog and stop accelerating, at the same time it made a ton of noise like it wanted to smoke the tires.

they blamed the engine, so i checked everything.

distributor mech advance, vacuum, compression, ignition timing, cam timing, fuel pressure, exhaust restriction, new plug wires, the works, and it was all the same. i even re-gasketed the entire top end, since it was leaking a bit of coolant. all checked out.

i slapped the wideband on it, and it was at ~17:1 WOT.

jet kits are hard to come by for this thing, so i got fed up and grabbed a regular set of drill bits (can't find my numbered ones, maybe I sold them)

knocked the primary jet open with a 1/16th utility drill

i figure i probably made a #160 jet instead of the #140 that was in it.

runs perfect now. wideband avg 13:1 wot, 15:1 cruise.

i'll order a jet kit, but it's no rush.

moral of the story is, even with a computer, don't forget carb logic. sometimes, after you're 100% sure it's a fuel delivery problem, you just have to throw a good amount of fuel at the poor beast where it's hurting the most, then fine tune from there. a bit more gas never hurt anything, that's why you can pour fuel into an engine from a pint glass and it'll run.

**Turbo Nasty** · 10-13-2017

Here's the bin from dyno day last January. It ran great on this tune for two weekends or so and then the car wouldn't run right on it anymore. It was too rich on the street.

And here's the stock chip copy from my car too for comparison.

**Turbo Nasty** · 10-13-2017

Originally Posted by steveo

also how about a datalog and an adx? i want to troll it for sketchy sensor output.

if the forum wont accept a file simply zip the thing or rename it to .bin and tell us what the old extension was.

I don't know how to start the recording with the datalogger yet. I will see if I can get the adx for you/