No worries; how far from Panama City are you? I got one more weekend here if you wanna get a personal Baseline tutorial.

 

What about Logging duration in ms and AF duration in ms??

 

I recently moved for work. I now live in Hampstead, NC. Its @20 miles north of Wilmington.

 

Bummer (I have only seen on 8 club-er since being here; ghey!);

Logging interval depends on the number of sensors your logging; if you pick them all I think it is 500ms for the AP.

The AF latency is 570ms or so I think; Chase would know.

And you can run a log to see for yourself too.

 

Here is what I now have after adjusting volts that weren't initially changed and adjusting to get a half decent curve. Apply this and go log more?

 

Much better - yeah go log on that tune (be sure to back up your stock one)

And look for your M Values to get smaller.

 

Just to clarify. I'm running Chases' tune, update with this MAF and log?

 

yes

 

Son of a monkey lovin' *****!!!!!! Car would not run! DAMN!!!!
After careful review, I noticed that I failed to extend the trends using Chaces' map and my logs were null and void. Started over and double checked everything and will run the map in its correct form and then do logs. Then, I will scale the MAF as intended.

 

so you logged running my map. you entered those logs in baseline and got a maf scale. you made the changes to my maf scale in racetuner. you saved the map and loaded it to your ap. then you flashed it, and your car wouldn't start?

that seems highly unlikely. wth? i are confused.

 

It would not stay running. However I will reiterate that it had to of been my fault for not extending the trends when I applied your maps to my "04" ATR. I did not complete the values. This all falls on me. Your map runs but, when I applied my M-values it would not run. Eratic idle then shut down. Reverted back to your tune and ran fine again.
I started from scratch and extended all trends and will get new logs and then apply the new m-values.
Again, completely my fault.

 

hmm. well, keep at it. let us know what's going on.

 

I am confused as well... try again and hopefully whatever you did doesn't happen again.

 

I double checked everything and loaded Chaces' tune. It felt much better than the first time. All except, low RPM range. A real slug. Feels like its bogging down when you stomp from a dead stop. Anyway. Logged some more and will apply those values tomorrow. These logs were very different from the others. Update tomorrow. Pending if I'm busy at work or not. Oh, the Rpm's after driving for a while settled at about 800 at a stop. At first, 1000-1100.

 

Let us know - hopefully a good log, and M tune will get you going.

 

sounds about right, chey.

is yours an auto? i'm almost never below 4k except for highway cruising, and even then, usually not.

keep tuning. you're almost there.

 

Yep. Its an auto. I'm getting ready to apply the m-values. I noticed the bogging/hesitation wasn't nearly as bad this morning.

I never got the chance to do a damn thing today. Actually busy at work.

Edit to include, bwahahahaha. My car is insane! Peculiar isn't it?

 

dude, what are you doing to your maf voltage? why does it say 2.34 so many times? no wonder your car died. holy ****. wow. NOOOOO!

you're supposed to multiply your m-values by the numbers on the bottom, the mass air flow. i should have been more clear about that.

so when you set up your maf in baseline, it wants the low numbers on the top 0.86, 0.98, 1.02, 1.05, 1.09, 1.13. then when you scale your maf, it sets those numbers next to your m-values. .86 maf volts corresponds to some mass air flow number on your maf calibration.

So if next to .86 on your baseline maf scale, you have an m value of 1.05, you go in racetuner and multiply the number BELOW .86 by 1.05. On mine,directly below .86 is 1.95. If baseline tells me my m-value for .86 is 1.05, i multiply 1.95 by 1.05 and leave .86 alone.

get it?

i don't think you need more logs. just revert to your working map, my map, and multiply your m-values correctly. then see what happens. i reckon then it will be time to lean out your fuel maps for maximum power -- rarr.

 

lol Wow
No wonder I gave up.
I'm too stupid to understand

 

I never ran this one. I was smart enough to know not to. Hahahahaha. Yes I must of misunderstood previously about changing the bottom number. M-value the top number, multiply the bottom. Got it! Man, I was so close to saying screw this, I'm far too stupid............... Will press on! Atleast now we all understand why it didn't run before. I applied the m-values incorrectly.

It actually gets easier. Definately still a lil difficult though. The only reason I keep posting my stuff is to help the baseline challenged, I make the mistakes that everyone can learn from.

 

Opps - yeah good catch chase!!!

I am honestly not a fan of how easy the AP will let you screw with the scales as opposed to the values.

But yes - your M values are to affect the BOTTOM row - the data not the top with is the voltage scale.

Hopefully, this will make things mo-betta.

 

I am gonna see if I can video me doing Justin's car in Seattle - and I'llpost it up so you get some commentary while working the software.

 

so i was helping chey last night over the phone. he's running the stock map. i checked his engine set-up. everything fine. i checked his logs, all open loop. i walked him through the import log and set-up template. we got a maf scale.

baseline was telling him he was 10 percent rich below 2.77 and 10 percent lean above 2.89. 2.77 and 2.89 were fine. i had him multiply one side by 1.05 and the other by .95. so we did half what baseline said.

when he flashed, he got pcm 335. weird. wth could have happened?

chey, is what i said here what you did?

 

I think that is a CEL that the AP sometimes trips... it happened to Bobby's car in Hawaii - I just re-flashed it again and did the 20 stomp reset and it went away.

 

Ya the AP can sometimes throw a fluke CEL, do a reset