Tacoma - OVTUNE - VFTUNER - Update Info and Original Development

Same issue here. I know there is an idle patch that I could try via opening a request ticket for it but I figured I'd wait for the updates coming soonish.

I really do think it has a lot to do with how the truck learns idle after flashing. 1.05 87 scored me great MPG and the truck felt more responsive. 1.05 91 does better than 1.04 on MPG but feels more sluggish than the 87 tune.

 

Same here, open a ticket. He sent me a fix.

 

Yes I emailed matt (support email) about it. Basically when you put the car into gear the RPM jumps to about 2k. Only happens to me when it was 28F or below though. But never had it after the "idle surge patch".

 

I'll try to be patient and wait for the new FM. Thanks.

 

Yeah, sounds like it is close to being released. I'd probably do the same.

 

I heard it should be soon.

 

Yeah... So put on your OV T-shirt and wait patiently . . .

 

Did you do it on an external drive? or use part of your internal?

 

Boot camp you can only do on the internal drive

 

Okay guys I have a huge data dump coming in the next few moments regarding a new version for the AT before we release the new Flash Manager.
check OP and this thread in about 20 - 30 mins

 

Question for you Fusion Savvy users: What number do you use to reference the number of misfires on a given drive cycle?

Details: Im running Fusion through Kiwi.
PID: The “all cylinders misfire” pid always reads 0 (when I’m watching it). I understand that it clears after a short time, but I’ve never seen it say anything other than 0.
Logging: The log graph shows activity, but I’m not sure how to read it (see image). @bshammer0 mentioned changing the axis to time, but I couldn’t figure out how to do that.
Mode $06: This monitor has two items that seem relavant: TID $0B and TID $0C.
I figured $0B applies a value of 1 for every 10 misfires for the last 10 drive cycles, but that’s not the case. I’ll log 10+ misfires on one cycle and then the very next cycle sometimes shows 0.
Previously, I was relying on $0C for the misfire count on the last drive cycle, but then I found the CSV file in the log folder. I figured if I add all noted misfires in the CSV file, I should get the same number as the $0C, but they are different numbers. The sum of the numbers in the misfire colum of the CSV file in this case is over 80. I’m oretty sure I’m not having 80 misfires...

 

I purchased the package a few days ago...was I supposed to send a registration request? lol

 

I'm hoping for my registration keys to come in. See what the hype is all about.

 

Look here and the adjacent posts...

 

No, you dont have 80, you need to count misfire for each cylinder to match it up to mode $06 $0C.
Add misfire PID for each cylinders

 

I linked a video earlier about doing it on an external drive and using up any of your laptops internal drive.

 

Thanks Mat!

 

Areee yourrrrr doongggleeesssss reeeadddyyy!!!!!!!

 

I know this may sound dumb but what is OP?