Using TM-Spy to see Model S data.

[Turbo3]

Man, so do you think having THREE Elm327 modules connected would yield all the data? We'd need to have simultaneous BT comm for that. I've signed up as a Tester and see the $4.99 app in the app store. I'm ordering the parts for the connector, now.

Google Play Store handles testers differently. Although it shows the temporary price of $4.99 it does not actually seem to charge testers this amount. All testers are listed as "Chargeable" whereas a real purchase is listed as "Charged" on my payments page. Don't know what happens when the test is over.

- - - Updated - - -

Version 0.0.6 is now out with support for saving and reading graph data. When you enable "Loop Reading Battery Power" only every 10th sample is graphed (so 10 samples/sec instead of 100 samples/sec). Graph now shows the last 120 seconds of data.

Graphing the points takes a lot of CPU power so you may get better data collection by not viewing the graph while collecting data. Try some full power runs both ways and see if you get a different graph depending on whether you view or not during collection.

Since I don't have a Model S to test changes on I am doing all the coding "blind" and need your feedback on how it actually performs.

Displaying lifetime charge/discharge energy should now show up in portrait mode.

I have a new email address for TM-Spy questions, feedback, screenshots and data files.

Use [email protected]

 

[Turbo3]

Version 0.0.7 is out. It has better formatting of the ELM trace file with better timing information.

Can testers taken an ELM trace with this version of a short drive and send it to me at the new email address listed on the About screen. See bottom of built-in Help for instructions on how to do it.

Be sure to exit and restart the app after enabling an ELM trace.

 

[faughtz]

0.0.7 now shows lifetime energy properly for me. Will do a trace later today.

- - - Updated - - -


I would prefer to see different (higher res) scaling for voltage and power on this graph, as well as milivolt resolution on the 96 module voltage graph.

Appreciate your work.

 

[Turbo3]

0.0.7 now shows lifetime energy properly for me. Will do a trace later today.

- - - Updated - - -


I would prefer to see different (higher res) scaling for voltage and power on this graph, as well as milivolt resolution on the 96 module voltage graph.

Appreciate your work.

Can you email me the F102_xxxxx.txt file from the TM-Spy/Graphs folder and I will see want I can do.

You save a graph by going into Freeze mode and pressing the Save button.

Is this what you meant by mv scale on 96 cell display?

 

[faughtz]

Can you email me the F102_xxxxx.txt file from the TM-Spy/Graphs folder and I will see want I can do.

You save a graph by going into Freeze mode and pressing the Save button.

Is this what you meant by mv scale on 96 cell display?

it is, for a balanced pack being able to see mv looks better- don't know how accurate the measurements are...

 

[Turbo3]

The question is how to scale these values. One is easy but with two there is a question of placement and the y scales to be used/shown. Any thoughts?

(ignore the right y-scale, just a test)

 

[faughtz]

I'd like to see more dynamic range.
You might check this thread for other thoughts:
Chassis CAN Logging To ASCII Text Plus Graphing.


I haven't looked closely, but I think your timescale in the graph is incorrect.

 

[Turbo3]

At low power the graph stops plotting data so as not to waste space.

If you are not using the special "Loop" option then time is not valid. Loop mode reads data at 100/sec and plots at 10/sec.

 

[Turbo3]

Here is the same plot with maximum amplitude without overlapping, each using half the screen. Now how to come up with a way to show the two y-axis scales each of which is using a different scaling factor.

Here is the original Insane mode graph using this method.

 

[Turbo3]

Here are the same two plots but now they share the same graph space.

 

[faughtz]

Here is the same plot with maximum amplitude without overlapping, each using half the screen. Now how to come up with a way to show the two y-axis scales each of which is using a different scaling factor.

Use the left y axis for voltage and the right y axis for power.

 

[garygid]

Eliminate (move) the fixed-text left axis caption, putting the same verbage
at the top of the graph where there is room.
Make that text red and blue to indicate the name of each plotted value.

Then, on the left axis put a column of red values on the major lines,
and add an adjacent column of blue values on the same major lines.

And, allow the user to specify, in settings, the Max and Min values
to display when rendering the graph.

Of course, the real data values would be stored, and values
off the graph area just not shown, as needed.

You might want to do this to handle the future Data Recipes anyway?

-------------
Note that the vertical scale of the cell voltages vertical bargraph can be
zoomed in to 50 mv full scale by tapping the bargraph below the midline
of the bargraph box, and zoomed out by tapping above.

Is 50 mv sufficient, where 1 mv changes can be easily disginguished, or is
a 20 mv scale necessary, where 1 mv steps would be very obvious?

- - - Updated - - -

We are wanting to display Tire Pressures, even if they are only found
on a different CAN bus. Has anybody identified where these values
appear, on which CAN bus, and in which msgID?

PM or email if you do not want the data location to appear "in print".
Thanks for any help.

 

[Johan]

On my car, the two Odometers matched, which probably means that the pack and the car
were married when they were both virgin, and have been together ever since. Cool.

I like this.

 

[MikeBur]

I'd like to see more dynamic range.
You might check this thread for other thoughts:
Chassis CAN Logging To ASCII Text Plus Graphing.


I haven't looked closely, but I think your timescale in the graph is incorrect.

ive been doing a bunch of the graphs and you really need ability to scale some factors on both y axis imo. When looking at rpm, for instance, you want to have speed(mph) on same axis and will need a multiple of mph, eg 10x mph and have just rpm and speed on one axis and rest of data, eg torque, etc on other; if you're focusing on power then you likely different axis and priorities.

my overall suggestion would be have to have multiple "templates" which are representing data user is after, eg. 0-60, 1/4 mile perf mode, range driving mode, battery charge mode, etc. of course having the ability to add a multiplier to each variable may be an advanced, and well-received, option ;-)

check out: Chassis CAN Logging To ASCII Text Plus Graphing - Page 16 and the google drive directory. I've put all the excel source files under there, incl. a geeky battery charging one. If you need more input, or help deciphering just let us know.

im just about to dust off an Android tablet I have, though looks like ELM BT logger I have is cheap clone... So will catch up and help as I can, though I'm traveling again as of tomorrow so receiving stuff is hard.

 

[jrreno]

We are wanting to display Tire Pressures, even if they are only found
on a different CAN bus. Has anybody identified where these values
appear, on which CAN bus, and in which msgID?

PM or email if you do not want the data location to appear "in print".
Thanks for any help.

Does the description of buses in this page help?

Undocumented | TeslaTap

 

[garygid]

jr...,
Thanks for the suggestion and link.
CAN6 (chassis) seems to be the correct place to look for TPMS data,
I just need to log that data as I drive and the tires warm up a bit.
Then, use CAN-Do's graphing to find 4 slowly increasing values.
Cheers, Gary

 

[Chris TX]

jr...,
Thanks for the suggestion and link.
CAN6 (chassis) seems to be the correct place to look for TPMS data,
I just need to log that data as I drive and the tires warm up a bit.
Then, use CAN-Do's graphing to find 4 slowly increasing values.
Cheers, Gary

Would it make sense to have a rotary switch that can select between the CAN buses? I'm imagining a selector in the app that would say "Pause collection", you turn the switch to the desired CAN bus, tell the app which CAN bus it's sniffing, then "Resume" sampling. Do we know if all 6 CAN buses are presented on this one connector behind the cubby?

 

[garygid]

Only 4 CAN buses are on the TDC, CAN2, 3, 4, and 6.
CAN3 is Powertrain, CAN6 is Chassis, and ... CAN2 is Body, as I recall.
The 4th CAN bus (CAN4 I believe) is Body Fault Tool, not so interesting
at this point.

The CAN2 and CAN4 are low speed, just 125k baud, and I suspect that
the ELM device can only read 500k and 250k buses.

For logging, my Adapter connects 4 (or 6) more wires, for 8 (or 10) total,
to allow me to log all the messages ... hopefully all the messages on
all 3 (or 4) CAN buses simultaneously.

Yes, a switch could be added, just be sure that is a break-before-make
type switch. Then, most likely, TM-Spy would be able to recognize the
user-selected CAN bus ... and show other interesting things, like
the tire pressures ... we hope.

 

[Turbo3]

Version 0.0.8 is now available for testing.

- Four new graph options.
- Defaults to a slower rate for graphing battery voltage and power/current of 10 samples per second allowing the graph to show the last 2 minutes of data. Does not graph data if power is less than 800 watts. The fast rate of 100 samples per second is still available.
- Graph can now be cleared.
- Graph scales are now colored to match graph color.
- Two new zoom in levels on 96 cell graph.

 

[garygid]

Offline (not in the car) the new functions Load / Clear / Save seem to work nicely.

It would be nice to have the same 3 functions for the "snapshot" data, so that
one can easily compare data taken at different times, like cell voltages when
parked, driving, and charging. The same Load/Clear and Save would be great.

The Calculate Power checkbox to graph Power instead of Amps is nice.
The Stacked Graphs feature is also very nice, and seems to work well.

The red color of the zero-power horizontal line seems slightly distracting,
so maybe green would be better?

The Cell Voltages in a P85+ while Supercharging are ... interesting.

It appears like each module has 2 low, 2 medium, and 2 high cells.
So, maybe the first 6 cell voltages are not all from the same module?
However, I do not see another simple ordering that makes sense.

Power and Voltage while driving, and near the end of Supercharging.

Great work, Turbo3 !