If you dont have the flashscan cable you will have to use your AC pressure switch to log AFR. If the AFR data isnt integrated into your logs you will have quite a task on your hands synching it up
yes I know about good luck on the wait, thus persuing this method
yes I am aware of using the ac pressure switch to log my wideband.
thanks for the heads up though, always appreciated!
Heath
98 Formula
Half-Assed Racing Custom STS kit in progress.
Its possible and doesn't take much to set it up, but I would just suck it up and get the entire package. I sold my HPT and came back and it was the best thing I have done in awhile.Originally Posted by Blackbird
if my OS ever becomes fully supported I will certainly be considering it.
until then I gotta be able to tune
Heath
98 Formula
Half-Assed Racing Custom STS kit in progress.
Is it totally NECESSARY to unplug the MAF? Can't I just leave it there?
Thanks
"All that is needed for the triumph of evil is that good men do nothing..."
You should be able to leave it in line, and plugged in. Just set '{C2901} MAF High Frequency Fail 1' to a value of 0.
Andrew
EFILive Crew
On hand smoothing the VE table: Should you smooth using the RPM(rows) or the columns(MAP) or both?
Bill
2011 Camaro 2SS/RS L99 RJT
CAI, Inc. Cold Air Induction;ADM Scoop
Rx Catch Can;Rx Breather;Roto-Fab Washer Container
VMax Ported RJT Throttle Body
XSPower Headers and XSPower 3" Exhaust System
Elite Engineering Tunnel Brace,
Gorilla Wheel Lock System;
Tinted Windows 35%;EFILive Tune
Uplugging the MAF is the only way to 100% sure get into SD mode. Whether or not you want to remove the MAF is totaly up to you. If you are planning on running SD all the time, why leave the MAF in line? It does restrict airflow.Originally Posted by The Highlander
On most cars, you can simply set the fail frequency to 0 to force closed loop. Some cars, mine included, didn't work like that. I had to actually unplug the MAF to get into SD.Originally Posted by Tordne
I installed my PLX M-300 this weekend (here are some preliminary notes including a wiring diagram). My car seems happy using the narrowband output so I took a crack at Autotune today. I drove around for about 20 minutes and ended up with the following map: Most of what's in the document seems reasonable to me except for one part. When creating the autotune config, we scale all of the VE entries (both primary and backup in my case) by 15%. Then later we scale them using the average results of the filtered maps. I believe this will undo the 15% for the cells we had good data for but doesn't it leave all the other cells ~15% too high? I would think that you would want to populate all of the "empty" cells with 0.85 so that after we scale the VE tables, cells we didn't collect enough data for are unchanged. An alternate way to do it would be to divide all off the cells by 0.85 and then scale the stock VE tables.
I must be missing something obvious; maybe I should be asking why scale the VE tables by 15%? Is it because we're running open loop and are going to be off and want to insure we're too rich instead of too lean?
One other point, we don't need to worry about zero'ing the LTFTs because that happens as a side effect of flashing the calibration, right?