Torque Pro App, running on windshield mounted tablet
04-27-2016, 07:49 AM
#61
Senior Member
My ELM327 module showed up last night, so I downloaded DashCommand to my iPhone and tried it out. Phone connected to the app easily, and the default gauges instantly came to life. App seems pretty comprehensive as far as data outputs, but I've found there are tons of Ford-specific data plug ins that you can purchase to monitor even more data. The only con I've come across so far is the 'add a gauge' function. It's not as intuitive as it could be. Unless I'm missing something, you have to build all the parameters into the gauge (C or F, min & max values, etc.). I thought I could just select 'cylinder head temp' and it would display the appropriately built gauge. It doesn't. You are basically selecting a PID input, and building the gauge to your liking around it...which isn't necessarily bad. There is a quick gauge, but it looks like it defaults to the tach, so you'd just have to modify everything to make it into the gauge you want. I keep thinking there has to be a better/quicker way to display a gauge for a specific data point, other than build it, but maybe I'm just missing it. I have a lot to learn about the app, but so far, it does what I need it to do.
I'm going to return the setup I purchased, initially recommended here, to Amazon (Android/Torque Pro setup). Not that there's anything wrong with it. I like that setup better, but since I already have an IOS device, using the $10 app and $10 ELM327 device makes more sense for me. I can use the extra $70 on something else.
I'm going to return the setup I purchased, initially recommended here, to Amazon (Android/Torque Pro setup). Not that there's anything wrong with it. I like that setup better, but since I already have an IOS device, using the $10 app and $10 ELM327 device makes more sense for me. I can use the extra $70 on something else.
04-27-2016, 09:45 AM
#62
LightningRod
@Mulestang
Two observations. You are expecting a LOT. You say - [the 'add a gauge' function not as intuitive as it could be - you have to build all the parameters.] That's a little like saying there should be one floorplan for building a house for anyone. A gauge for CHT is very different from one for CATALYST Temperature. One user might like to display O2 sensor data in volts - 0 to 5, the next might like a graph, the next a histogram.
The other observation. You say - [I have a lot to learn about the app,...] It is not a bad thing, but the App was just the beginning of what all I wound up learning when I started using my scanner app. My 5.4L 3v has approx. 220 different PIDs it will report (most are unpublished), and after three years, I'm STILL uncovering additional information that is lurking around inside that ECU.
But the 'hacking' is fun, and very useful in keeping our trucks running right.
HAVE FUN.
Two observations. You are expecting a LOT. You say - [the 'add a gauge' function not as intuitive as it could be - you have to build all the parameters.] That's a little like saying there should be one floorplan for building a house for anyone. A gauge for CHT is very different from one for CATALYST Temperature. One user might like to display O2 sensor data in volts - 0 to 5, the next might like a graph, the next a histogram.
The other observation. You say - [I have a lot to learn about the app,...] It is not a bad thing, but the App was just the beginning of what all I wound up learning when I started using my scanner app. My 5.4L 3v has approx. 220 different PIDs it will report (most are unpublished), and after three years, I'm STILL uncovering additional information that is lurking around inside that ECU.
But the 'hacking' is fun, and very useful in keeping our trucks running right.
HAVE FUN.
04-27-2016, 10:58 AM
#63
Senior Member
@Mulestang
Two observations. You are expecting a LOT. You say - [the 'add a gauge' function not as intuitive as it could be - you have to build all the parameters.] That's a little like saying there should be one floorplan for building a house for anyone. A gauge for CHT is very different from one for CATALYST Temperature. One user might like to display O2 sensor data in volts - 0 to 5, the next might like a graph, the next a histogram.
The other observation. You say - [I have a lot to learn about the app,...] It is not a bad thing, but the App was just the beginning of what all I wound up learning when I started using my scanner app. My 5.4L 3v has approx. 220 different PIDs it will report (most are unpublished), and after three years, I'm STILL uncovering additional information that is lurking around inside that ECU.
HAVE FUN.
Two observations. You are expecting a LOT. You say - [the 'add a gauge' function not as intuitive as it could be - you have to build all the parameters.] That's a little like saying there should be one floorplan for building a house for anyone. A gauge for CHT is very different from one for CATALYST Temperature. One user might like to display O2 sensor data in volts - 0 to 5, the next might like a graph, the next a histogram.
The other observation. You say - [I have a lot to learn about the app,...] It is not a bad thing, but the App was just the beginning of what all I wound up learning when I started using my scanner app. My 5.4L 3v has approx. 220 different PIDs it will report (most are unpublished), and after three years, I'm STILL uncovering additional information that is lurking around inside that ECU.
HAVE FUN.
Yes, I expected too much out of it's 'intuitiveness'. When I entered my specific vehicle data, and selected a coolant temp gauge, I expected a gauge that resembled the parameters and limitations of my specific vehicle. What I got was a gauge, in Celsius, that read from 0 to 70000 degrees. I figured out how to 'mod' it, so it was no big deal. Not diminishing the value of the tool at all. Only putting myself on report for expecting too much. Pretty impressed thus far.
Question. When I go to create a gauge, and some of the options are locked (have to purchase add-on), are they all 'onesy twosies', or can you purchase all the ad-ons in a lump?
**EDIT: Duh moment. Never thought to Google for a user's manual: https://www.palmerperformance.com/do...ser_Manual.pdf
Last edited by Mulestang; 04-27-2016 at 11:21 AM.
04-27-2016, 11:39 AM
#64
NIGHT TRAIN
Thread Starter
i'm running the FULL Torque Scan on my truck right now...
04-27-2016, 12:21 PM
#65
LightningRod
The CHT ---- oh no
@ Mulestang
Please forgive me for laughing... No malice is intended. It is just classic that the 'cylinder head temp' is the first sensor you focused on. It is perhaps the most complicated one under your hood.
You said: [I figured out how to 'mod' it, so it was no big deal]
I have spent HOURS and HOURS logging the CHT and trying to reverse engineer an "S" curve formula that will accurately represent temperature from that little bugger. I'm not ready to give up - but for now, but the ECT (a value calculated by the ECU) is the closest I have gotten. See the Attached OBDII theory page for engine temperature and the Conversion table.
If you monitor the CHT, you'll notice that the reading seems to decline for a while, then start going back up - where it stablizes. The ECU places a bias on the CHT and does a "rationality check" or "calibrates" it on each 'drive cycle' if 'soak time' exceeds 2 hours ---- etc. etc. etc. etc.
You might find this article interesting: http://www.searchautoparts.com/motor...ure-cht-sensor
I still don't have a suitable formula worked out. I'm no mathematician, but I haven't figured out how to put the table or build an Array in Troque Pro.
NOW THAT I'VE HAD MY CHUCKLE AT YOUR EXPENSE, you can have a laugh at my expense if you read through this thread: https://torque-bhp.com/forums/?wpfor...topic&t=5657.0
Like I said earlier. HAVE FUN.
---------- EDIT
To remove a little bit of the mystery:
PID# 1685 is the actual CHT SENSOR itself and = the ECU bias voltage - I think from its A/D converter.
PID# 1624 is the Cylinder head "temperature" that has already been calculated by the ECU in some ºC form. The formula I'm currently using is (((A*256)+B)*1.999)+32 . The +32 is intended to give me ºF reading. I think it reads a little bit low, (at around 245º when ECT is approx 195).
Please forgive me for laughing... No malice is intended. It is just classic that the 'cylinder head temp' is the first sensor you focused on. It is perhaps the most complicated one under your hood.
You said: [I figured out how to 'mod' it, so it was no big deal]
I have spent HOURS and HOURS logging the CHT and trying to reverse engineer an "S" curve formula that will accurately represent temperature from that little bugger. I'm not ready to give up - but for now, but the ECT (a value calculated by the ECU) is the closest I have gotten. See the Attached OBDII theory page for engine temperature and the Conversion table.
If you monitor the CHT, you'll notice that the reading seems to decline for a while, then start going back up - where it stablizes. The ECU places a bias on the CHT and does a "rationality check" or "calibrates" it on each 'drive cycle' if 'soak time' exceeds 2 hours ---- etc. etc. etc. etc.
You might find this article interesting: http://www.searchautoparts.com/motor...ure-cht-sensor
I still don't have a suitable formula worked out. I'm no mathematician, but I haven't figured out how to put the table or build an Array in Troque Pro.
NOW THAT I'VE HAD MY CHUCKLE AT YOUR EXPENSE, you can have a laugh at my expense if you read through this thread: https://torque-bhp.com/forums/?wpfor...topic&t=5657.0
Like I said earlier. HAVE FUN.
---------- EDIT
To remove a little bit of the mystery:
PID# 1685 is the actual CHT SENSOR itself and = the ECU bias voltage - I think from its A/D converter.
PID# 1624 is the Cylinder head "temperature" that has already been calculated by the ECU in some ºC form. The formula I'm currently using is (((A*256)+B)*1.999)+32 . The +32 is intended to give me ºF reading. I think it reads a little bit low, (at around 245º when ECT is approx 195).
Last edited by F150Torqued; 04-27-2016 at 05:11 PM. Reason: To add PID #'s relating to CHT