Live Data

I have a 2009 tundra with a 5.7L

For those of you that are well-versed on second generation tundra, scan data. I have the following question.

Should I be able to read VVTi variations in my scan data. Providing of course, that my VVTi is working properly with which I believe that it is.

All lines of data pertaining to the VVTi remain at zero at all times, regardless of driving conditions. I have no trouble codes and no drivability issues.

The scan tool that I am using is an Xtool D8 bidirectional unit. Beings it is a bidirectional unit I can go into actuation tests and command the VVTI. The engine responds with a rough idle as expected. So I know that it is capable of responding to commands. Yet all data remains at zero.

Of course I’m inclined to think it is the scan tool but I wanted to see what other people have seen on their scanners?

I appreciate any pertinent input, thank you.

 

I've got a 2013 IS-350 and 4.6 2010 Tundra, and can report the same. No data is present.

What I haven't done is looked through Techstream to see if their utility allows us to watch it?

PS - as I know it, most of the tuners have yet to break into the valve train maps and modify them. I'm taking a WAG that Toyota encrypted it somehow???

 

Randy,
Thanks for the information. Since you mentioned TechStream, I assume you are a Toyota dealership mechanic? If you wouldn’t mind taking a peek at the VVTi data on the Techstream next time you’re using one. I certainly would appreciate it. Obviously if the Techstream can’t read the VVTi data, then it can’t be done.
Seems odd that Toyota would encrypt just that data and allow access to virtually everything else but who knows?

Thanks again, Tim

 

I am not that. Just an owner who has spent a lot of time working on vehicles. Having three Toyota's in the stable, somewhat justifies buying in to the tooling.

I don't use it often, but it has my curiosity if it's there.

 

If I remember correctly not even DOT and the department of highway safety could get that info. When all those Avalons and Tundras had "unintended acceleration" I don't remember the process that it took, but do believe Obama had to sign an EO or something along the lines to make Toyota comply with the data. Apples to Oranges the Mark 4 Supra needs a standalone ECU to go full potential. The new Mark 5 Supra's ECUs are locked out 2020 on...

 

Techstream records VVTi data, this is a log I have of a short drive (2.5 mins) around my neighborhood. Resolution is low as I was logging all parameters in the ECM. The only variation I see is VVT Control Status #1 and #2 comes ON from OFF not long after engine startup but none of the other variables had any change from 0. I only picked a few of the variables for VVT #1. I am also not sure what conditions need to be met for the system to start to function and actually vary..........

I guess a longer drive on highway and all around could show potentially better data.




Here is the full list in the ECM parameters

 

VVT-i after startup is more like injector duty cycle controlling oil flow which in turn controls intake and exhaust cam timing with relation to crankshaft position which varies from take off to cruise speed.

If you can read the sensors, they should report the difference in angle relative to crank position.

Aim angle and change angle would be meaningful unfortunately no data which is what I've seen using other hardware.
Aim = desired
Change = actual angle

I wonder why Yoda hid this from us?

 

A big thank you to both Jeff and Randy for providing this information. It’s a big help to me because now I will stop blaming my non-OEM scanner.

My Xtool D8 is bi directional so I can command the VVTi on and off and it does respond. Engine idles, rough as expected. I just wasn’t able to read live data pertaining to the system. But since now I know that the TechStream also cannot, I’ll put that into the category of, ‘is as it is’. Thanks again.

 

Jeff, what version of Techstream are you using?

 

Its an older “internet” version like 16 I think. I need to take the time to upgrade to 22 or 23 I don’t remember the newest one.

I use it to log data on OBD then match the graphs up to CAN data for the ECUs. Has worked pretty well but time consuming.

Reading data off the broadcasted CAN network is much faster than OBD request and response. For example I can read a speed signal from the Abs ecu 30x a second or somthing like that. Rate is very fast.

Most the OBD scanners have the UDS read by identifier values programmed in and use OBD request and read to show data