Tacoma - OVTUNE - VFTUNER - Update Info and Original Development

I cannot *confirm* it will work, I was just hoping it will. My past experience with toyota is that they will cut cost any possible way, so my GUESS is that the cylinder heads on the new LS500 are the same as the 2GRFKS.

Most likely it's a 2GR base variant, so it uses a 2GR block. which is already old as hell.

going as fast as I can to get this 1.02C completely tested, configured, perfected.

 

I haven't received any tunes yet, because I haven't yet sent @OVTune my stock files. I'm waiting until I get the latest updates from the dealer (hopefully this week). But I think that since 1.01b seems to be the most widely praised version to date, I think it would be nice if Matt would provide that version to EVERY tune customer. I'm planning to ask for it when I email my stock files to him later this week.

 

I've seen 2 already!

 

I'll buy this tune when it is specifically released for MT. Rev hang driving me nuts too. I've found I can make it not do it if I release the throttle at a precise time compared to disengaging the clutch. But I can't do it every time. I usually just shift without matching now, and slip the clutch out to drag the engine speed down. Which I am ok with, but it's the only vehicle I have to drive this way.

 

Nothing but an oil like ran to it!

Then I think we’d need to do something funky with the ECU since we don’t have a MAP sensor.

 

update for everyone reading

few emails for people asking for 1.01/1.02 (B). you'll receive today

folks to messaged that they want to wait on 1.02C, you will receive 1.01B/1.02B as well as 1.02 (on release)

 

IN FOR THE

 

@OVTune Given the significant updates being done to 1.02C, why not increment to a 1.03, 1.1.0 or 2.0.0 instead of calling it 1.02c? All these variations of 1.02(a, b, c) seems confusing.

 

But we already came up with the slick sounding 1.02CrispyCreme

 

You can rename it to whatever you want when he mails it to you

 

From a software development standpoint you typically have a v.m.r.f release structure and increment your version or release or mod level (i.e. the v, r, m in the v.r.m.f) with each code drop to the field when new function is present and which you choose is dependent on the significance of the new function targeted. An increment for the fix level (i.e. the f in the v.r.m.f) is typically reserved for fixes only and no new function. So in the case of what has been described as being worked on for 1.0.2.c it appears to be new function (i.e. shift enhancements) that was never present in previous releases and not fixes to existing functions. This is why I suggested the break from the 1.0.2.c to a release versioning that better described the significance of the content being delivered.

My suggestion to @OVTune was purely to better align with SW development practices so the end user better understands the significance of each code release to the field.

 

I have no idea what that means, it sounds real, but I sure can't wait for 1.02CrispyCream

 

https://youtu.be/ItmY6XAVW9M

 

Rather than worrying about how the tunes are labeled, he needs to stay focused on actual development, testing, and delivery since a 4 week wait really sucks. He can label it "jackass edition" for all I care as long as the thing works great and improves the truck's drivability.

 

Somewhere a PMs head just exploded...

 

Just driving in the 15 mph wind!! Flat surface.

 

Mine did this towing on Sunday, I thought it was because it's a new trailer and I'd not towed it before but it does seem like an issue. No amount of accelerating or decelerating made it go to 5th/6th, especially using cruise.

 

Yours is in yellow? Mine is always green no matter how low.

Edit: always blue

 

Mine is always Blue

 

Cant you just set the color in the Multi-Info Display? I used to have it blue, and now I have it set to Red...

Edit: Page 96 of the owners manual (for a 2016) https://www.toyota.com/t3Portal/document/om-s/OM04005U/pdf/OM04005U.pdf