Slashdot Mirror
Tesla Roadster Data Logging Format Reverse Engineered
s1axter writes with word that "the data log format for the Tesla Roadster has been reverse engineered and documented, now available in Python. (Python script linked in the post.)" From the linked blog entry: "Not only was I given a $110k car unrestricted I was requested to see what ECU information is available, collect and parse the data from it. Tesla Motors periodically collects information from their vehicles presumably to see what real-world driving the cars see. On original Roadster models there is no method to collect this information remotely thus someone must go out to the vehicle and collect it. The owner of the vehicle saw this and wanted to know what information was collected on these service calls ... Because I am a big fan of freedom to modify a program to fit ones needs, I have uploaded the ... python script to parse Tesla logs."
logs for an overpriced pile of duck shit
What an achievement, copying a file from a filesystem over USB. A real reverse engineer would have picked a more complex problem (like a real mass production car) and not tooted his own horn on slashdot after making such minor headway. Hope your principal recommends you graduate from high school a year early, or whatever, s1axter.
The Tesla has a gas engine and so by law must have an ODB II port for emissions control. Why bother with propritary hackery when you can just plug in and take advantage of existing hardware and diagnostic toolsets?
Which makes sense given how some i4 engines can approach the same levels of power to that of a v6.
Most I4 engines in European cars are more powerful than American V6 engines. I mean, Ford are still releasing engines based on the ancient Essex blocks, albeit drilled out to 4 litres, but they're still thirsty, clattery gutless boat anchors. Hell, the I4 turbodiesel in my van is quieter and more powerful than most Yank-tank petrols...