Tacoma - OVTUNE - VFTUNER - Update Info and Original Development

Ticket submitted

 

It *IS* important to let Mat know about something like misfires so that he can help you directly. But I for one think that bulletin boards such as this are the perfect tool to let people discuss issues like this.

Yes, this discussion can indeed be painful and disruptive, as some people do assume what they are seeing is tune related. But this is a case were each owner has it within their power to measure before and after each tune. We need to encourage reporting both pre and post numbers. Perhaps we need to encourage even more info re: warm-up vs. after warm up, etc.

Reporting and discussing has in the last few posts alone revealed the need for a new flash procedure most people were not aware *might* need to be done in order to "reset learned values" - on SOME trucks (post 38175 - "disconnect battery immediately after flash").

Although apparently an issue caused by Toyota's ECU/flash design, this one thing alone *could* account for what *some* people have experienced. Mat has stated he is investigating and actively working on other issues.

Reporting to Mat directly, not through the forums, is *required* if you expect Mat to help address your problem and more importantly understand the scope of any particular problem (number of trucks with similar issue). He needs a way of knowing how often something is happening.

But reporting or asking others for their experience here is just as important for *entirely* different reasons.

 

Thank you.

For everyone that has submitted tickets. I just want you to know I DO SEE THEM. I have reviewed them. Just because you have not got a reply, does not mean you are being ignored. I am taking all of this information and doing testing.

It will take some time but I am working on this as quickly as I can. Continually posting the same thing on here, or submitting the same tickets, will only slow the process down (not saying anyone did, just saying). I see and am fully aware of the issues. It's very difficult for me to answer tickets all day long and get anything else done. SO I am working on this with my truck further, as a result some tickets will not get an answer.
that does NOT mean you are being ignored! I just want to post that again as I have said it many times.

 

Just a quick question.... so on the stock tune I could definitely feel and even hear what sounded to me like misfire/ spark knock. On 105 87 and 91 tunes (havent tested 93 yet) I dont have the same feeling or audible indicators but I do feel what could be some sort of hesitation under high load low acceleration situations (cruising along in a higher gear low rpms but slowly accelerating). Not that I want to go looking for more problems but does mat have a logger that he has sent out that I could use to verify what I could be feeling? I do have a ticket and have exchanged a few emails with him but he hasn't come out and asked me to log anything yet. I just want to be able to be on the list of those who have the issues discussed if/when the next release is sent out.

 

I have sent loggers out to some people and am working on a PID update for the logger. (logger will be available for everyone when new FM releases)
Regarding your issue.. it's the same problem that has and exists since stock. It's always been a problem for some, regardless of tune, (although some tunes seem to enhance the already existing issue) so we don't need logs because we are already aware of what it is.
Finding out exactly what causes it is the mystery. It's some bug or bad table in the stock ECU from Toyota. I'm quite certain it's ignition related at this point but the ignition scheme is literally more complex than rocket science.

 

I am using my own data logger. Kiwi3 + OBD2 Fusion App

 

@OVTune Instead of unplug battery for 5-10 minutes, would "clear DTC" achieve the same result? Or clearing DTC does not reset the target area of ECU memory that control those learned values?

 

It should, but at this point I'd say nothing beats unplugging the battery. It's not even specific to this Tacoma, but Toyota ECUs in general. The only way you know in older ones that a reset is done right is the engine should stall right after you start it. Which ... doesn't make sense..

 

I tried this - I was on a long drive last weekend and things didn't seem right (long list I won't go into here) so I pulled over on the interstate and hit Clear DTCs over my OBD app and I can confirm this did NOT completely clear the RAM on my truck. Disconnecting a battery cable does the trick. Always keep a 10mm in the truck!

 

Good to know, thanks guys

 

Some good reading for the performance-minded folks... either this guy knows his stuff or is an absolute master in bullshit...

https://www.tacomaworld.com/threads/2020-tacoma-teased.590296/page-28#post-19748341

 

Always keep a 10mm in the truck!

[and then you know where to find it].

 

gotta say that was a very interesting read. and if he's a bsmaster he's damn good. (see what i did there?)

 

Wasnt trying to pluck a nerve. I do agree that issues have existed since before you came along. But what I meant was the issue changed the way it displayed itself, atleast to me. You are a man of extreme patience in my book for putting up with toyotas over engineered ECU and I'm pretty sure I can speak for all of us and say we greatly appreciate what you've done so far.

 

Any reason I can't downgrade to 1.04 (non-R) from 1.05? Or do I have to goto stock first then to 1.04? The 3-5/5-3 thing is driving me crazy and I think i'm just going to wait until Matt has a chance to update 1.05 for it.

 

If you have updated to the TSB, then 1.04 (non-R) is incompatible. If you have a 16-17 and never updated to the B04 (assuming AT) TSB Toyota calibration, then 1.04 is still compatible.

If you have the TSB though, do not flash 1.04(nonR)

 

Interesting read

 

Can someone let me know which PID in OBD Fusion to use to show drive cycle misfires instead of the "All Cylinders Misfires" PID? I thought I saw it a ways back, but searching on "misfires" brings back a lot of posts...

 

Go to Monitors, then hit the 3rd tab on the bottom (Mode $06). All cylinder misfire count for an entire drive cycle will be toward the bottom of the list.

 

Thank you sir! And thank you for not raining fire down on me for asking something that was probably in an earlier post