vF Tuning for Manual Transmission 3rd Gens

What do you guys think about asking for a table axis SIZE increase. Like the PTTT or G1 tables (or whatever they're called now).. I was thinking about more cells on x axis for example (throttle angle I think?).
I know this means changes to the EROM, not sure about PITA level for Mat.

 

I think more resolution on several tables would be helpful. I don't think Mat ever said which tables would have that option. I've been waiting for that feature to come out too.

 

I'm not sure that it would do that much.

The two examples i posted a couple pages back, the second one i was working on i scrapped. The difference between values was very minute but the changes to throttle behavior was very different.

That map is touchy, I'm not sure how anyone can daily with the values that Matt had in there. They were great if you were looking for super responsive and pure acceleration, but when you are in the city or traffic it was annoying fighting it.

The first half of mine is actually the stock gear 1 map, merged with the gear 4 map in the middle, merged with Matt's at the top.

 

PTTG1 has the same values as Gear 5. I ended up using the values in Gear 6 instead.

 

@tonered

updated this post with my modified agm tune

 

Thanks. I edited the link in the 1st post.

 

Well, i finally got around to getting obd fusion and an adapter so i can keep an eye on different pids.

Should make it easier to play.

Turns out that my typical cruising range for the pedal is around 26% and my typical acceleration range is around 50%.

Also turns out that pushing the throttle beyond 50% doesn't net me an increase in throttle opening. Basically I've limited my throttle in my maps.

I kinda already knew that. With that being said, I'm gonna try some different testing that doesn't limit the throttle in preparation for the new throttle maps that are incoming.

 

It is good for general monitoring, but the data rate is pretty slow compared to logging as you know.

Both are great tools within their limits.

 

yeah but it does give some clues into what you are doing. Such as knock feedback, misfires, throttle position and throttle angle, valve advance and ignition advance.

I am hoping that i may be able to "see" what makes it go tuggy tuggy on the hills under load.

 

Or not, my adapter won't connect.

It connected 2 times over the weekend and now nothing

 

I had a Carista BT adapter that was wonky on arrival.. sent it back and got a second one, all good since.

 

What was the result?

 

I did it along with the ALC changes that I made. I don't have any data other than butt dyno feels better.

 

Thank you, sir.

 

I left it unplugged after i got to work and tried it on my lunch, it's working now. Who knows.

I may exchange it. It's the cheap veepeak

 

Well, here is the first run with obdfusion

It's 87 octane reg file with 89 octane fuel.

No modifications other than the maps i showed previously and some acis

At first the knock correction learned value was around 22. And the feedback typically around -3, which i see is about normal.

When i found a spot that took a bit more throttle in the 2500rpm range, load of about 60 to 70% the knock feedback went between -5 and -7 and the learned value dropped to 17.

From what i understand a knock feedback value of -7 is not ideal

Interesting note, which i think it's more related to the ignition and throttle efficiency tables, you can apply light throttle and the throttle angles won't change from 0, but the ignition will advance. I suppose that is where it chooses the most efficient way to increase torque and will add timing rather than throttle to give the demand for torque you are after.

I wonder if that could be the key to the lumpy feeling.

 

im going to continue thinking out loud.

The Power and Torque ratings at the top of the picture above are from the "calculated" Pids. I chose nM for torque because it "matches" the values in VF.

I noticed today, that in certain gears the torque value goes well above the rated value for the truck. First gear is too fast to update on OBDFusion, but second gear you can get a better picture.

I saw values over 550nM in the "calculated" map. Im assuming this is some sort of multiplication, possibly gear ratio that affects it.

I also am assuming this is why some of the Torque based maps have values over 700nM in them.

It will be nice when some of the PIDS hit the logger on VF because i think we may be able to use them to fine tune things

 

I like your thinking out loud. Tons of great info. I just don't have good input to add most times.

 

By all means, keep it going.

 

Unfortunately a lot of those torque tables cannot be logged without running a special patched version file.