Data Logging - Problem with hardware/software/other?
01-06-2011, 11:52 AM
#1
TECH Fanatic
Thread Starter
iTrader: (6)
Join Date: Feb 2009
Posts: 1,360
Likes: 0
Received 0 Likes
on
0 Posts
Data Logging - Problem with hardware/software/other? I leave the tuning to the pros, but data logging is something I have the tools for laying around.
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).
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.
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).
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.
