So, I took my Goat to the dealer and had them hook it up to their ECU reader. Oil Pressure was read at about 35 but their reader would not give them the PID for that Sensor. So, there is a PID for the Oil Pressure. Just got to figure out now what it is, lol.

To calculate the atmospheric pressure entry required for your boost gauge to read correctly you can pull up the "Barometer" gauge and enter that number in decimal. If the Barometer reads "108" then enter in the boost gauge atmospheric pressure number as "10.8". Sea Level is 14.7 and the higher in elevation you go the lower that number gets. I'm at 3279 feet above sea level and my barometer is reading 108 so I entered in the boost gauge atmospheric pressure correction number as 10.8 for a accurate reading of my boost.

Hm, I really ought to try to make that automatic as I can work out (rough) elevation from the GPS (some vehicles don't support baro readings).

I'll have a think and might add this as an option in a later version!

In for the LS section. I haven't plugged in for a while since my GTO is in winter hibernation but I am interested in updates specific to our needs.

Subscribed.

I am having a bit of difficulty with logging my LS setup.

Current Setup:
China ELM 327 Bluetooth OBDII Scanner
HTC EVO 4G w/ 16GB Class 10 MicroSDHC Card
Torque Application for Android - Set to 0.1 second intervals

Current Procedure:
Enable Bluetooth on EVO
Set IGN to key ON engine OFF
Run the Torque app
Wait for Connection to ELM 327
Toggle data logging on
Set IGN to RUN
Log away

My problem is with the data being returned and I don't know if the problem is with the sampling capability of the Chinese ELM 327, the Bluetooth capabilities, 16GB Class 10 MicroSDHC Card(doubtful), or the Torque application/processing speed of EVO(Clocked to 1.15 GHz w/ rooted Sense ROM). The data will remain constant for anywhere between 0.8-1.4 seconds or 8-14 lines of data, but NOT uniformly across the columns (See screenshot below). I now see the warnings of the Chinese adapters, but it connects just fine (I had the adapter prior to purchasing Torque). Could the warnings imply slow data transfer as well?

Notice in the images below that GPS Speed logs slow too, which, if I am not mistaken, is entirely processed in the phone. That would rule out the cheap Chinese ELM unit and Bluetooth, BUT is that a correct assumption?

This is annoying considering when I went on a spirited drive, the data was blotchy at best and any results I derive from this data must be taken with a grain of salt. So, what do you guy's think?

Obviously, I am not operating at 128%+ VE, that's due to errors within the data updating itself! I think 93% is still kind of high considering my power output and choking top-end/exhaust.

Engine Specs: 2002 T/A, 408 w/ 799 heads, MS4 Cam, LS6 Intake, Mac Mid Headers, etc. - Stock ECU tuned by professional.

Quote from admin on January 6, 2011, 12:39
Hm, I really ought to try to make that automatic as I can work out (rough) elevation from the GPS (some vehicles don't support baro readings).

I'll have a think and might add this as an option in a later version!

Why don't you just check for barometric input, if it exists (and seem to work) - just subtract that live value. Will be much better than GPS height, the GPS hangs and sometimes don't work in my experience...

Quote from admin on January 6, 2011, 12:39
Hm, I really ought to try to make that automatic as I can work out (rough) elevation from the GPS (some vehicles don't support baro readings).

I'll have a think and might add this as an option in a later version!

Re: Boost Gauge

Someone suggested adding a editing function to create our own custom gauges. You may want to consider that?

Quote from 1SLwLS1 on January 6, 2011, 23:51
I am having a bit of difficulty with logging my LS setup.

Current Setup:
China ELM 327 Bluetooth OBDII Scanner
HTC EVO 4G w/ 16GB Class 10 MicroSDHC Card
Torque Application for Android - Set to 0.1 second intervals

Current Procedure:
Enable Bluetooth on EVO
Set IGN to key ON engine OFF
Run the Torque app
Wait for Connection to ELM 327
Toggle data logging on
Set IGN to RUN
Log away

My problem is with the data being returned and I don't know if the problem is with the sampling capability of the Chinese ELM 327, the Bluetooth capabilities, 16GB Class 10 MicroSDHC Card(doubtful), or the Torque application/processing speed of EVO(Clocked to 1.15 GHz w/ rooted Sense ROM). The data will remain constant for anywhere between 0.8-1.4 seconds or 8-14 lines of data, but NOT uniformly across the columns (See screenshot below). I now see the warnings of the Chinese adapters, but it connects just fine (I had the adapter prior to purchasing Torque). Could the warnings imply slow data transfer as well?

Notice in the images below that GPS Speed logs slow too, which, if I am not mistaken, is entirely processed in the phone. That would rule out the cheap Chinese ELM unit and Bluetooth, BUT is that a correct assumption?

This is annoying considering when I went on a spirited drive, the data was blotchy at best and any results I derive from this data must be taken with a grain of salt. So, what do you guy's think?

Obviously, I am not operating at 128%+ VE, that's due to errors within the data updating itself! I think 93% is still kind of high considering my power output and choking top-end/exhaust.

Engine Specs: 2002 T/A, 408 w/ 799 heads, MS4 Cam, LS6 Intake, Mac Mid Headers, etc. - Stock ECU tuned by professional.

Re: Data Logging

I haven't even tried to log yet, but those numbers are all over the place. I would try several things, reduce the ping frequency, move to phone memory, try logging in a low populated area like the back roads to eliminate interference. I think I'm going to try logging next. Good Luck.

Quote from CALNURS on January 8, 2011, 14:45
Re: Data Logging

I haven't even tried to log yet, but those numbers are all over the place. I would try several things, reduce the ping frequency, move to phone memory, try logging in a low populated area like the back roads to eliminate interference. I think I'm going to try logging next. Good Luck.

I tried a few different things over the weekend. I dramatically reduced the Number of PIDs to log, I added a different SetCPU profile that set a performance priority to the phone's processor (when logging), deleted all but (4) gauges on the phone's screen, killed all running apps, put the phone in silent, etc. Still, logs look just as blotchy. The only thing I can reduce is the sampling frequency, but this shouldn't be a problem with my ECU. I am going to try this and then I will also get a Bluetooth/USB scanner and see if that helps.

I just purchased the full version of torque today. Here is my setup:

2009 G8 GXP
M6
Factory Bluetooth

It connects to the OBD, but all the dials say "no data".

Can you send a 'comms debug log' (menu option) to me with your forum name at the top and I'll have a look.

Re: Logging speeds

Need to clear this up as it's just how the logging works 🙂

All the adapters can only scan PIDs (sensors) from the vehicles at the rate the ECU will allow them to be read.

This means, that if you set up logging for a line every 0.1 seconds, and the ECU will only supply 4 readings per second, that you're basically going to see a lot of duplicate lines in the log.

The reason for this is because not all ECUs are produced equal, some provide data at extremely fast speeds, and some really don't (usually toyota ECUs are quite quick as an example)

GPS on the phone will only update as fast as the correlators can provide accurate data - this is typically once a second on most GPS chips in android phones.

So, just to recap, if you have logging set to one line every 0.1 seconds, and have a slow ecu, then you're going to see a lot of duplicate lines. You probably want to reduce the logging frequency. Also, only log the PIDs you absolutely need as on slow ECUs they take time to read - so the more you have, the longer a full sweep of all the sensors will take.

Hope this clears things up. For interests sake, Torque itself can log well over 300-500 PIDs/second, it's just the ECU that is the limiting factor.

Ian

So where can I find a list of supported sensors, or is Torque complete and reads all the sensors a particular vehicle contains?

Thanks,

Torque is not complete for each vehicle. Not all sensors are standard. The "extended PID's" are exclusively licensed by GM. For example, oil pressure is not listed. However, if you find out the PID you can enter it manually into Torque.

Here are some interesting post regarding the complexity of PID's that may or may not shed some light on PID identifying. Maybe some super smart guy or the Developer will read this and come up with some ideas on the Oil Pressure PID. Good Luck!

http://www.obd-2.de/dl/probs.txt

http://www.hptuners.com/forum/showthread.php?p=1474

In for LS section. Just learning about this app and I am very interested in learning how to take advantag of all of the information.

Quote from CALNURS on January 20, 2011, 22:36
Here are some interesting post regarding the complexity of PID's that may or may not shed some light on PID identifying. Maybe some super smart guy or the Developer will read this and come up with some ideas on the Oil Pressure PID. Good Luck!

http://www.obd-2.de/dl/probs.txt

http://www.hptuners.com/forum/showthread.php?p=1474

Bump to the top for more PIDs on the LS engine.

GTO Ponitac-Holden/Vauxhall Monaro specific ones all the better. 🙂

I have not been able to get the 0-60, 1/8 mile, and 1/4 mile timing functions to work. (I have good OBDII and GPS connections)

I also have not been able to accurate readings from the HP and Torque functions. I recently had the car dyno tested with over 460 RWHP and 450 RWTQ. The reading are low by over 100 HP and 100 FTLB's. Not sure if readings are supposed to be flywheel or rear wheel numbers, but either way they are way off. Any suggestions would be greatly appreciated. (I have entered the weight and displacement accurately)

All other readings are good and I am very impressed with the app. I bought the app to monitor the info going on under the hood, and that is working beautifully.

Best regards,

Jeff

The 0-60 and 1/4 mile functions should be working for you if you have good GPS and OBD.

The most important thing for the readings, is that you don't decelerate between shifts too much, and don't spin the wheels as well. Make sure the correct weight is in the settings.

Ian