When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I recently upgraded to a new android phone. The Bluetooth version is 5.2. It seems it's not communicating with the VeePeak adapter. I feel the car wants to stall out while it's reading live data. The data is slow to refresh while using OBD Fusion as well.
I had no problems like this with my previous phone that had Bluetooth 5.0.
The good my phone pairs for hands free, and head unit. I hoping maybe a software update on the OBD Fusion app could fix the issue.
Just got the OBD Fusion app to check KCLV values and decided to play around with the dashboards. I created the below for fun and when I went to test it out I noticed I'm unable to get a Engine Oil temp gauge to work (not shown below). I'm guessing it's a limitation of the PIDs and what the car reports? I also saw that Lance stated in an older post that "The ECM is completely unaware of the oil temperature."
Just got the OBD Fusion app to check KCLV values and decided to play around with the dashboards. I created the below for fun and when I went to test it out I noticed I'm unable to get a Engine Oil temp gauge to work (not shown below). I'm guessing it's a limitation of the PIDs and what the car reports? I also saw that Lance stated in an older post that "The ECM is completely unaware of the oil temperature."
Yeah i've been around the forum for ages now. Started with the IS350 back in 2006 and moved on to the IS-F in 2008.
After the add-on pack does the scan, it shows you what sensors have data. That said, not all PID's with data have valid PID calculations to obtain data.
An example is anything cam timing related is not available which makes me wonder if Toyota encoded it someway making it inaccessible? As I know it, not even the tuners have access to the VVT-i code to modify. Is that a coincidence?
Cayman, take a look at the schematic to the gauge cluster. It could be that they never digitized the signal and it goes straight to gauge as analog. I find this plausible if the -F also uses a low pressure switch to trigger a light. Does it have two sensors?
Also, can you read the oil temperature? IIRC doesn't the -F lock you out of higher RPM's until the water and/or oil temperature are at a minimum safe value? i.e. >165°F or something like that?
After the add-on pack does the scan, it shows you what sensors have data. That said, not all PID's with data have valid PID calculations to obtain data.
An example is anything cam timing related is not available which makes me wonder if Toyota encoded it someway making it inaccessible? As I know it, not even the tuners have access to the VVT-i code to modify. Is that a coincidence?
Cayman, take a look at the schematic to the gauge cluster. It could be that they never digitized the signal and it goes straight to gauge as analog. I find this plausible if the -F also uses a low pressure switch to trigger a light. Does it have two sensors?
Also, can you read the oil temperature? IIRC doesn't the -F lock you out of higher RPM's until the water and/or oil temperature are at a minimum safe value? i.e. >165°F or something like that?
I recently upgraded to a new android phone. The Bluetooth version is 5.2. It seems it's not communicating with the VeePeak adapter. I feel the car wants to stall out while it's reading live data. The data is slow to refresh while using OBD Fusion as well.
I had no problems like this with my previous phone that had Bluetooth 5.0.
The good my phone pairs for hands free, and head unit. I hoping maybe a software update on the OBD Fusion app could fix the issue.
It looks like everything was fixed on the Fusion side. I actually like the ease of the new dashboard settings redesign. Everything feels more fluid and snappy. Though the refresh is still laggy. Even with the fast polling active. VeePeak seems to only support BLE on IOS, and not Android.
To make it worth wile I only use about 8 PID's other wise you get too much lag. Having too many dashboards will create a slow refresh.