@amund7 , I have a few questions about SMT....
- Are there other data streams on the buses that we just don't know enough to report(or haven't discovered) , or does the ALL tab show all the bus data that the cars generate?
- Why do I see actual data on my RWD TM3 for "front oil flow", since I obviously don't have a front motor at all.... what is this data that is reported?
- Have you been asked to allow/show calculated values? For example it would be nice to use SOC x constant = Range in miles, or show 1 - [(SOC x constant) / 325] = battery degradation % ....
Thanks again for a fantastic app. The data geek inside me loves it!
1. There are many buses, depending on car model. Comma.ai controls steering and throttle through one of the other buses for Model S, and has decoded a lot of signals on that bus. Check their comma cabana software. Our wiring setup can easily be rewired/re-pinned to pick up different buses, but the app won't understand. It could however capture the raw data (CAN dump), then analyze that data on PC, if you have the definitions. It would require some better hardware to capture more than one bus at the same time. Comma.ai has the Panda, that I believe can get 3 buses simultaneously. But this is (currently) far outside the scope of Scan My Tesla.
The other buses has some cool stuff, such as doors/windows/wheel speeds/tire pressures/suspension heights (for air suspension), but I think most of the community agrees the Powertrain bus, which we are on, contains the most interesting info, I think there is no drive unit or battery info on the other buses.
2. I believe the front & rear oil stuff has been swapped in recent firmware updates, I am aware & it's on the list. That means, what you see is really your rear motor.
3. Lots of calculated values in Scan My Tesla. Model S and X reports numerical range, but it's not a straight constant, I believe it has a kink near the bottom. I just discovered the range numbers in Model 3 as well, it will be included in an update soon.
Thank you for your kind words!