Connect car via Tronity vs ODB2

[ViWe]

Description:  Detailed description of the feature you want to add.

Use Case: Describe how you would use the feature, or how often.  This helps us assess prioritization on new features.

Remember, the more details you can add, the faster we can build out new features!

Edited January 31, 2022 by ViWe
Question added: what is the difference in car data used between Tronity vs ODB2 connection. How is historical data used? How is live data used?

[Samuel-ABRP]

OBD provides real time live data of many things that remote APIs normally do not provide and are also delayed. For example from OBD we get battery temperature, voltage, current, soc. Most APIs do not report temperatures and current/voltage in realtime. So with OBD we can create a much better consumption model for your personal driving style based on the data you provide. Remote APIs are mostly only convenient for having the SoC avbailable so you do not need to manually configure it.

But in the end it depends on the API. Which car are you talking about?

[ViWe]

Thanks for this elaborate reply. We drive a Seat Mii and a Kia EV6. 

[Samuel-ABRP]

I think both these APIs are not detailed enough to get much more data than SoC.

[ViWe]

On 2/3/2022 at 6:51 AM, Samuel-ABRP said:

I think both these APIs are not detailed enough to get much more data than SoC.

Ok, good, ODB is the way to go then.

Wrt building up the consumption model for my personal driving style, I think this means I should be driving with ABRP as much as possible, even when it is a shorter trip on which I don't need to charge underway? Or is the consumption model build up every time (for every trip) anew?