yeah, i was thinking just for the accessport.

i'll be for getting results up soon, captian.

what % are you talking about>? in baseline?

 

Yeah - under view my tunes; there is a Percent to Add or Remove 3D map you can look at one you click the "Red" Button and tune the car.

This is assuming your MAF is good to go.

 

Hey Kane, is there any reason this wouldnt work with access 2000? Newest version of Office I have is Office 2000. If you think it will work I'll give it a go :

 

just try it and see. 2000 is pretty old.

 

It might - I coded it in 2000; so it SHOULD be ok. But no guarantees...

 

I dont do enough spreadsheets or presentations to justify buying the newer versions

I"ll give it a go

 

Let me know man - thanks.

 

I work alot the next couple days, but I'll at least try to get it setup and start taking logs one of the evenings.

I need to start playing with my cobb and getting familiar with the software anyway. Probably a good idea to do it before I put my turbo on

 

delete that giant pic. i got you.

 

so kane, you said that's NOT BAD, right? That's the one running the maf scale i did in sarasota. i didn't have much log data either. however ...

i still don't have logs for runs on my latest maf calibration using 1.5.

and i'm worried now that my estimations are off when trying to fill in the M value gaps. it would be better if baseline could match the intervals used in the map. I know you mentioned something about that, but i"m just reminding you, and letting others know where they have to be careful.

this is what happens when someone who has no idea what he's doing makes guesses.

i need to just draw a smoother curve through there and use those numbers, i would think, right?.

 

Yeah - I want to see the logs of your latest MAF calibration... I agree that the curve looks funky... and I do need to add the MAF table as soon as I can.

However, you need to realize the software needs a lot of data - so the best bet is to log like a bastid and then run it through the MAF scaler to see your changes.

As for the Baseline maf you sent me that I made that graph off - it is pretty close; a few lean spots - but overall your in the 13.5-12.5 sweet spot.

Also remember that the fuel map in Baseline needs to match the fuel map in your AP...... or the measurements will be off.

 

did you get my email Kane ?

 

Yep - I just need some more info from ya... emailed back.

BTW - why did you hand key your map... copy paste works on the Protuner....

 

i know i'm where i want to be with the afrs. but i thought the goal was to get to where you're getting exactly what you enter in the fuel map. there are still some spots where i'm having to pull down the afrs, so to speak, to get want i want.

i logged the **** out of that map. i fed baseline an assload of logs; i gave it 20 good 30 sec or longer logs.

i posted my m'values from that. then when i scale the maf off that, and make my guesses, i get the funky green line.

i'm sure i'm doing something wrong, as usual.

and i'm asking what you think i should do as far making better guesses for the gaps. do you think i should scale the whole thing up higher by the same factor?

i figured folks including me would benefit from what you say, homie. not complaining at all.

 

I am confused a bit.... can you call me bro to make sure I know what you mean?

 

Ok - talked to Chase.... seems like we have two possible issues - AFR latency and the fact that the M Value Scale does not directly tie into the MAF volt scale in the AP - so we are gonna split the difference.

Chase is gonna test his latency and I'm gonna add a "smarter" MAF scaler to the software.... then we will see what happens.

 

edited for clarity.

thanks for calling.

 

Just tried that again ---- I can't get it to copy & paste ?????

 

That coincides with my experiences so far as well . It seems you can have your maf scaling give you a perfect result for WOT but then be up to 10% off at part throttle . That is what i've found anyway . So ATM i've split the diff - seems to work pretty well ......

 

13 - 20.1 in the very next row. less than half a sec.

 

i should have thought of this before.

a set up stock NA engine baseline setup is here.

just import logs and go.

edit: change af latency to 500 ms for accessport and change your fuel map in baseline to match the one you ran when you logged.

 

Bretus (Control C to copy and Control V to paste) try that.

Chase etc... I'll be setting up the new MAF tool this morning I was sick yesterday.

So chase - the latency is 500 ms? One row of your log.... interesting; I think we should set that up - especially when I went to 590 ms for my AFR and saw a much smoother tune.

 

well, hold up. maybe it's two rows. didn't look at the rpm before.

14.7 4757
14.55 4762
14.7 4751
13.96 4602
20.14 4552
20.14 4349
20.14 4181


14.26 5506
16.46 5451
20.14 5217

 

DO that again with Accel Position too.

 

15.6- 14.55 4762
15.6 - 14.7 4751
0 ---- 13.96 4602
0 ---- 20.14 4552
0 ---- 20.14 4349