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.
Having a problem using the torque pro app in that the engine oil temp listed in the pids for the Ford 6.0 does not work, have researched several forums and others have had this problem, I have tried running program on both android cell phone and android tablet, both will not display oil temp. There have been several different pid formulas and have tried 3 to no avail. This one seems to work for most but will not work for me. ((((A*256)+B)/100)-40)*(9/5)+32 , I am using the PID: 221310. Any suggestions? All the other apps work good.
I started out with that one, which is the regular pid for our truck. Whats weird is that under normal extra pids it is listed and is green, but when I go to add the EOT it is not green, but black, therefore it does not work. Like I mentioned this is the only gauge that does not work.
I used one of the PIDs and didn't get an EOT reading either but then looked again and found a second one that was working. When you add PIDs and the truck is running you can see all the ones that are actually getting info. I'm actually hoping the reading is a bit off as my EOT was getting really high, over 230 at times while pulling but guessing it's accurate and I have a (less than year old) oil cooler starting to clog. I can look this afternoon when I get home what PID it is but I know I didn't do a custom for that one and maybe the equation is off. Either way, you might want to add one while connect to the truck and while you scroll through all of them you'll be able to see the ones actually sending a signal.
Making small progress, I made custom pid using number from my original post above, and named it in lower case: eot, at least it saved this time, now I can add this custom pid and it displays but is reading -44.626
I used one of the PIDs and didn't get an EOT reading either but then looked again and found a second one that was working. When you add PIDs and the truck is running you can see all the ones that are actually getting info. I'm actually hoping the reading is a bit off as my EOT was getting really high, over 230 at times while pulling but guessing it's accurate and I have a (less than year old) oil cooler starting to clog. I can look this afternoon when I get home what PID it is but I know I didn't do a custom for that one and maybe the equation is off. Either way, you might want to add one while connect to the truck and while you scroll through all of them you'll be able to see the ones actually sending a signal.
Thanks, I will wait if you could check your settings.
So the long name for the one I’m using is:
[FORD]Engine Oil Temp and the equation it has is
(((A*256)+B)/100)-40
I did not create this one, same as LasVegas F250 it appears.
The provided one did not work, so was experimenting with others. I have ordered a new bloothtooth adapter to make sure.
Rod: did Torque show any comms errors with your current adapter? Had you tried slowing communication speed down or adjusting any of the other adapter settings? Be nice if you had somebody near you that could just throw on a simple SGII and know the sensor is good (EOT and ECT are the same type sensor, so you could swap them too...)
I did try the fast and slow settings, the only pid that does not work is the EOT, I do have a scangauge II and it reads perfect oil temp so its not sensors, I also tried on a friends truck which is same as mine and it has the same issue of not reading oil temp, I did order a new adapter today.
I did try the fast and slow settings, the only pid that does not work is the EOT, I do have a scangauge II and it reads perfect oil temp so its not sensors, I also tried on a friends truck which is same as mine and it has the same issue of not reading oil temp, I did order a new adapter today.
I'm betting that must be it -- my 1st adapter was bad, but I had a number of weird readings, then again it kinda' looked like it was working... You've chased this one enough... Good luck!
Scott