Doh. Yes the integral. Thanks for catching it.I assume you meant the integral (wrt time).
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Doh. Yes the integral. Thanks for catching it.I assume you meant the integral (wrt time).
Thanks Doug! Works great.
Is there a way to set a starting trip and keep it saved (maybe set last trip as well)? It defaults to 1989 or something then there around about 20 trips or so done while it was in production to scroll through.
Looks like I'm getting close to the 300 Wh/mile everyone talks about.
Can't get it to work. The program displays an error message ("The parameter is incorrect") as soon as i try to load the log file.
My VIN is displayed correctly, but that's it.
I tried two log files, created a new one today, tried two PC's but the error remains.
Doug, did you get my log file to work on your PC?
Tomsax has shown that you can use the derivative of the speed to get a reasonable estimate of the distance.
I just uploaded an update. This version includes an estimated Wh/mile (or km) display.
[/QUOTE]
Doug, for MY2010 you don't need to to estimate the wh/mile. It's in the drive10m record. if the length_byte >=22 then buf[3+19] is the first byte of a four byte long that is the whpm. Divide this value by 4.0 to get the actual Whr/Mile. I'm pretty sure it was in the last version of my [URL="http://www.teslamotorsclub.com/showthread.php/4032-Log-Parsing-tool-available?p=52602&viewfull=1#post52602"]log parser[/URL]
I've sent you a PM with info on how to parse the data for the Daily records for battery capacity, temp, & soc. With this you should be able to plot the Ah Capacity of the battery vs time back to the birth of the car! Separate histogram plots of the SoC and temp will show how well the battery was cared for :)
Doug, for MY2010 you don't need to to estimate the wh/mile. It's in the drive10m record. if the length_byte >=22 then buf[3+19] is the first byte of a four byte long that is the whpm. Divide this value by 4.0 to get the actual Whr/Mile. I'm pretty sure it was in the last version of my log parser
I've sent you a PM with info on how to parse the data for the Daily records for battery capacity, temp, & soc. With this you should be able to plot the Ah Capacity of the battery vs time back to the birth of the car! Separate histogram plots of the SoC and temp will show how well the battery was cared for
Really interesting tool. One thing that sprang out, something that was niggling in the back of my mind... Hey TM, have fun on the 'Pre-delivery check'?
LOL. Of course it might be done on a dynamometer...
Actually whr/mile was in the log_parse_v15 release. While your at it, you might want to add elevation too. IIRC It's a INT16 that starts at the 8th byte after the length field.Okay, I went by Tom Saxton's document... I guess some other things have been discovered since. I'll add that in, and fall back to the current method if the information isn't available.
Actually whr/mile was in the log_parse_v15 release. While your at it, you might want to add elevation too. IIRC It's a INT16 that starts at the 8th byte after the length field.
Sounds like it's time to update Tom's document. (hint... maybe you could mark it up and pass it back to him for agreement...?)
Awesome work, Doug! If you're still looking for a log from a 1.5, PM me.
My document was never intended to be comprehensive. I just wanted to document what I knew, mostly stuff I figured out plus a few fields Scott helped me with. Scott was ahead of me from the beginning and has learned a lot more since I wrote that document. I'm hoping Scott will eventually be able to release the source code for his parser which will serve as documentation for what he's learned through heroic effort.
Awesome work, Doug! If you're still looking for a log from a 1.5, PM me.
My document was never intended to be comprehensive. I just wanted to document what I knew, mostly stuff I figured out plus a few fields Scott helped me with. Scott was ahead of me from the beginning and has learned a lot more since I wrote that document. I'm hoping Scott will eventually be able to release the source code for his parser which will serve as documentation for what he's learned through heroic effort.