very interested on it.

Also interested

I'll clean it up a bit and post something in a day or two..

worked on it a bit this morning...

YES, that looks very interesting.

Hi!

You may want to look at the torque sync agent (now available) that will automatically sync the data over wifi to the PC and put it into a predefined location - you may find it easier to point your code at where the data is synced to:

{home directory}/.torqueRecorder folder (it only syncs trip logs and tripRecorder logs at the moment)

The sync agent (windows, osx) is on http://torque-bhp.com/wiki/Exporting_Video

This should save the hassle of connecting a cable to retrieve logs as over wifi it's mostly automatic as soon as the phone and PC see each other

Thanks for the suggestion piemmm, I'll definitely look into that. Sorry I haven't gotten anywhere with this guys, been swamped with work recently. Certainly still going to do this thing!!

Hi volDeus - How is your logging viewer coming? I would be interested in using it also.

Thanks
superdog404

What are you using? If it's C# I may be able to help. Are you willing to share your source code?

O boi... 3 year necro... sorry.

I realize there are some other solutions available now that have progressed excellently, but I spent the last hour dusting mine off and polishing it a bit for personal necessity... I always seem to find my own way of doing things.

I still plan to add all of the fancy features, life gets in the way... I can throw it up on GitHub if anyone wants. (Yes it's c-sharp)

Working on dynamic scaling and weighted guide rules. Considering porting to Android. Threw together a WPF UI that feels cool also....

Got a little more done on it..

Been putting in some quality time with this. Complex expressions can now be entered for graphing and CSV log data accessed as variables in those expressions.

This means, for example, you could define a graph as simple as "RPM[x]” or as complicated as "(O2UP[x+10] - O2DOWN[x]) / THROTTLE[x]"

Each graph (or "Data Visualizer") also has other attributes affecting it's appearance that can be set to a static value or controlled with an expression as well.

For instance, a "visualizer" rendering;
-RPM could have it's "Scale" attribute set to a small magnitude so that it fits on screen with other data.
-Short term fuel could have it's x-axis origin line defined by the expression "STTRIM[mean]” to center at it's average value.
-Absolute load could have a gradient overlay with it's start and stop defined as "ABSLOAD[min]" and "ABSLOAD[max]".
-O2 sensor voltage could incorporate data from a different parameter and have it's "Opacity" attribute defined as "COOLTEMP[x] * (100 / COOLTEMP[range])".

The possibilities far exceed my imagination or knowledge of tuning/diagnosis.

All visualizer definitions are automatically saved to view later or with another set of data. They can also be exported or imported through XML.

I plan to add a feature to import data sets from sources other than torque CSV files, and to export the data set resulting from an expression. This could be used for comparing known data from technical documentation and/or exports from a vehicle operating within specifications, to one that is being diagnosed or tuned. It could also be used to compare data from the same vehicle but at different times and in different situations/configurations.

Currently the only style of visualizer is the "Linear Curve" shown in the images I posted. I plan to add others but I haven't thought much about what they will be.

@volDeus

I am quiet interested in your efforts. Similarly, I have been working on discovery of non-standard (proprietary) PIDs available on my vehicle and creation of meaningful dashboard gauges for analysis of a rather common problem with the popular Ford 5.4L three valve engine's (the Variable Valve Timing system - and Cam Phasers). The ECU turns off a 'flag' (VCTENA) and disables (shuts down) the V.V.T. system based on logic that I am trying to reverse engineer. Each run cycle (not drive cycle as no Soak time is required), VCTENA starts off in the "ON" state, and after some count (???) of CAM retard error ("CAMERRR") occurrences, or some other yet undiscovered parameters??, the ECU turns VCTENA "OFF" for the balance of that run cycle. Shutting off the engine and restarting it 'even immediately' restarts that cycle - EVEN after and in the presence of a DTC. Excel graphs from Torque CSV logfiles are helpful, but its too 'tedious' to change source data ranges to scan along magnified views of longer (condensed) time periods. One of the several "counters" maintained by the ECU determines when a DTC (P0011 or P0012 /or/ P0021 or P0022) - over advance or performance / over retard on banks 1 or 2 respectively) is set. It is based on an accumulation of CAMERRR degrees or counter of how many times CAMERRR exceeds so many degrees. Determining the specific "COUNT" that leads to these DTC's - and under what condition(s) the ECU will reset them to avoid setting the code would be invaluable diagnostics / troubleshooting information.

If you would be interested in any cooperative effort, or testing of a paid or unpaid beta version of the Visualizer, you may PM me at the private email address Temp_volDeus_from_Torque@devoll.com . That discussion would be more appropriate outside the Forum.

Looks great, is it possible to get a compiled copy of that?

Quote from volDeus on May 1, 2015
Been putting in some quality time with this. Complex expressions can now be entered for graphing and CSV log data accessed as variables in those expressions.

This means, for example, you could define a graph as simple as "RPM[x]” or as complicated as "(O2UP[x+10] - O2DOWN[x]) / THROTTLE[x]"

Each graph (or "Data Visualizer") also has other attributes affecting it's appearance that can be set to a static value or controlled with an expression as well.

For instance, a "visualizer" rendering;
-RPM could have it's "Scale" attribute set to a small magnitude so that it fits on screen with other data.
-Short term fuel could have it's x-axis origin line defined by the expression "STTRIM[mean]” to center at it's average value.
-Absolute load could have a gradient overlay with it's start and stop defined as "ABSLOAD[min]" and "ABSLOAD[max]".
-O2 sensor voltage could incorporate data from a different parameter and have it's "Opacity" attribute defined as "COOLTEMP[x] * (100 / COOLTEMP[range])".

The possibilities far exceed my imagination or knowledge of tuning/diagnosis.

All visualizer definitions are automatically saved to view later or with another set of data. They can also be exported or imported through XML.

I plan to add a feature to import data sets from sources other than torque CSV files, and to export the data set resulting from an expression. This could be used for comparing known data from technical documentation and/or exports from a vehicle operating within specifications, to one that is being diagnosed or tuned. It could also be used to compare data from the same vehicle but at different times and in different situations/configurations.

Currently the only style of visualizer is the "Linear Curve" shown in the images I posted. I plan to add others but I haven't thought much about what they will be.

I am very interested in your project. It has been about 10 months since this thread's last post. This seams to be exactly what I am picturing for a viewer. I am unable to find a decent torque log viewer and am hoping someone if not you could point me in this program's direction or another like it. It would be much appreciated as now I am dealing with Excel and as we all know it's borderline conducive.

Thanks for any help.