Printable View
greg got a chance to play with v2
just loaded it and messed with a few things
i have an issue with the fuel pump run mod i have it setup to run with the clutch in but it runs by itself for a long time with or without the clutch
did i miss something
also for the NLTS am i understanding the this works when the cruise switch is turned on ?
kx
You need to have the clutch cruise power kill switch wired into pin 67 of the ECU. None of the "clutch mods" will work without this. I'm working on instructions for this.Quote:
Originally Posted by Kx1984
Front feed back is 4FQuote:
Originally Posted by dyter
Rear feed back is 0F
Front primary O2 voltage is 3E
Rear primary O2 voltage is 13
The O2 voltages are more important to log than the trims.
lol ahhh okQuote:
Originally Posted by Greg E
i guess ill wait till u finish up
antilag works nice lol that works hahahaha
kx
Hey Greg, so I'm getting closer to getting this thing running right. First I installed my innovate wbo2 and now I'm able to datalog my wbo2 readings. Next, I had to rescale my Delphi 1000cc injectors down to 913cc on ECUflash because at 1002cc scaling my spark plugs became carbon fouled out! They looked like this, even darker!(not my plug) http://3.bp.blogspot.com/-Qn4cJDQzoB...lediridium.JPG :( Plus my exhaust tips were blacked out, it started smoking out the tailpipe as well looked bluish but it wasn't burning oil just running super rich. Now I'm not sure exactly if this was a result of the car just running overly rich or a result of the start up tables which weren't previously adjusted causing them to foul out. Regardless, its not throwing out clouds of smoke any more and seems to be running better but still smells putrid and toxic. I also installed new plugs as well. However I have not adjusted the latency tables or the fuel maps yet.Quote:
Originally Posted by Greg E
I went out last nite just cruising on the expressway at a steady 60mph to try to stabilize the LTFT(mid) fuel trims.. Front bank on Evoscan shows 1.4XXX and rear bank is 3.4XXX is that much of a variance normal? On evom I was reading we should try to have the trims near 0 as much as possible. Also found this:
LTFT (mid) => cruise
LTFT (low) => idle
If low ~= mid & both > 0 then decrease injector scaling
If low ~= mid & both < 0 then increase injector scaling
If low > mid then increase latency values
If low < mid then decrease latency values
I want to adjust my trims and latency values but dont want to mess with too many variables just yet until I get my head wrapped around this thing. Whats this you're saying about its more important to log o2 voltage instead of the trims?
Finally, I did a few WOT pulls on the untouched timing/fuel maps. I saw 12.1 on the wbo2 from 3500rpms to 5XXX rpms then it tapers down to 10.9 till redline?!? I'm running pump 93..wasn't knocking. This thing is confusing the heck out of me...I'm running wg boost..about 7lbs on the 19T's. Got any input? I really need some...lol
I'll post up a log tomorrow
I think I know why its running so lean...its the heads.
that wot AFR is not that lean, especially at 7 PSI. The ecu is not going to see a ton of load. Log the load and compare it to the fuel map.
Exactly. The MAF smoothing (VE) table and the fuel table are set up for stock turbos. These both are going to need some major over haul especially when you're running turbos cable of 3x the airflow of stock.Quote:
Originally Posted by Forest Gump
Start with the VE table. Log 2 byte airflow, 2 byte load, RPM, your wideband and the fuel table lookup AFR. Compare the wideband numbers you see to the fuel table. Adding more VE gives more fuel. Less leans out the mixture. It works kind of like an SAFC. This is what takes the most time and since every single car is unique, I can't even give you a good base map.
Eventually after many logs and tweaks, you'll get to the point where the VE table is setup so well that the wideband numbers will match the fuel table numbers within a couple tenths of a point. On my 98, I got it so perfect the fuel table matched the wideband perfectly.
People try to compensate for the engine modification changes in VE by playing with the injector scaling and fuel table to compensate. While this works, I feel its not the best approach. Maybe I just need to make my own version of "how to tune a 3/s".... It's actually easier to run the injector scaling/ latency values, set the fuel table to the AFRs youd like to see and adjust the VE table till your wideband matches your fuel table. It's got fewer values in it. ;)
Where can I do some reading so I can get a better grasp of this concept of tuning with ecuflash that you're talking about because everything related to tuning on evom is way different than what you're saying. :)
Secondly, should I aim to adjust cruising afr's first then WOT runs or what? My car sucks on gas...I would really like for it to get at least decent gas mileage. What should I do get better mpg? I don't want to waste too much time with the WOT pulls on 93 pump, I'm going to tune for WOT on e85.
Also is there anyway to slightly speed up the datalogging value for the wbo2 it seems like its *slightly* lagging behind the guage unit. Not sure how much it matters or even if its normal??
I've been contemplating doing my own write up thread. I kinda hoped guys would figure this out on their own.
No way to speed up logging however, you can get up to 33 samples per second by logging with the SD card. Before Dyter, I hadn't ever played with it. Was quite surprised by the difference in packet speed.
Are you logging the wideband thru the serial port on your laptop or thru pin 93 of the ECU?