GM Volt Forum banner

Voltage, an Android app for Volt

2 reading
54K views 208 replies 57 participants last post by  Volty123  
#1 · (Edited)
Hi everyone,
I created a simple app since I didn't find one that can easily visualize battery voltages (MyGreenVolt didn't work for me).

Currently, it shows:
  • Battery cells 1-96 voltage, Min, Avg, Max, Spread (disbalance mV)
  • Battery capacity, KWh, %
  • SoC displayed, SoC Raw
  • Distance traveled

Every reading is stored in the embedded time-series database, so aggregations and analysis are possible in the future with previously collected data.
Currently, the only parameter plotted over time is battery capacity. But I believe, there are other useful PIDs that can be visualized in a history chart.

It was tested with my 2016 Volt, a generic ELM327 Bluetooth adapter, Android 7, 9, and 11 devices.

Your feedback, suggestions, and tests are very welcome.

It's available on Google Play as a public beta:


GitHub: voltage

Here are some screenshots of it:



The app uses the following permissions:

android.permission.BLUETOOTH
android.permission.BLUETOOTH_CONNECT

These are necessary for communication with ELM327


Looking forward to hearing your thoughts
 
#2 ·
Downloaded. I'll give it a whirl this week and let you know. 2017 Volt LT.

You might want to specify what Android permissions are required, though.
 
  • Like
Reactions: thx
#4 ·
it's not tested yet, and I will appreciate if someone will try it with Gen I and send the logs in case of failure (Settings -> Send logs)
 
#6 ·
I’m curious to know how Battery Capacity is being defined (perhaps Ah readings, multiplied by a chosen "nominal voltage" value?), and why it might change over short time periods as it does in this example. The posted screen shot seems to show the capacity readings for the 2016 Volt from 29 June 2023 to 14 August 2023 (~ six weeks) falling measurably.

29 June: ~16.76 kWh?
~5 July: 16.56 kWh
22 July: ~16.43 kWh?
~3 August: 16.38 kWh
~9 August: ~16.33 kWh?
14 August: 16.29 kWh

Chart notes Mon, Jul 24, capacity 16.433332 kWh
Chart seems to show loss of ~0.5 kWh of capacity over a six week period, so the Jul 24 date is the half-way point reading of the graph or just the average capacity over the six week period???
Original capacity 2016 Volt battery = 18.4 kWh, so 16.29 kWh is ~(16.29/18.4 =) 88.5% of original? And with current full capacity of 16.29 kWh and an Electric Mode window of ~76% of full capacity, this 2016 Volt should be seeing ~12.4 kWh Used per "one full charge?"
 
#8 ·
I think the chart shows the actual degradation of my Volt's battery during this summer. However, the vehicle is connected to a charger 24/7 and cools down itself when it's hot. After every ride where more than 70% of the charge was used, I noticed a decrease in this value. I hope it will slow down falling at some point.

As for the capacity calculation, I use PID 2241A3 which I dumped from the CarScanner app. After googling this PID I found some mentions either on this forum or Bolt forum and I figured out the formula:

(decimal representation of 2 last bytes) / 30

It produced the same results as the CarScanner app did. I still use it as a reference.
Here are the recent screenshots of both apps:


Regarding the * KWh Used value on the display, I should check when I will have a ride that will use all charge.
 
#7 ·
Awesome project, thanks for making it open source.

Downloaded, but it will not open/ immediate crashes for me. OnePlus7T, lineageOS 20 (nightly 20230820) which is Android 13. I'll see if I can get you more useful crash info when I have time to dig into it in a day or two.
 
#9 ·
Thank you for giving it a try, I will try to run it on the Android 13 emulator. If you could dump a stack trace via the Android studio or ADB / platform-tools, I could analyze the potential reason for the crash and make a fix. Feel free to PM me if you need assistance on that.
 
#10 ·
Awesome project, thanks for making it open source.

Downloaded, but it will not open/ immediate crashes for me. OnePlus7T, lineageOS 20 (nightly 20230820) which is Android 13. I'll see if I can get you more useful crash info when I have time to dig into it in a day or two.
Thank you for giving it a try, I will try to run it on the Android 13 emulator. If you could dump a stack trace via the Android studio or ADB / platform-tools, I could analyze the potential reason for the crash and make a fix. Feel free to PM me if you need assistance on that.
I downloaded it but it immediately crashed for me as well. Pixel 6 Pro on Android 13. 2016 Gen II Volt.
MyGreenVolt / MGV is working OK. 11 mV spread (disbalance).
Image
 
#15 ·
...
As for the capacity calculation, I use PID 2241A3 which I dumped from the CarScanner app. After googling this PID I found some mentions either on this forum or Bolt forum and I figured out the formula:

(decimal representation of 2 last bytes) / 30
Hi; I'm the creator of the MyVoltControl iOS app. Congratulations on your new app!

The things you are currently showing will also work just fine for gen-1 Volts (but with a few changes to your equations).
Note that the battery capacity PID you are using does not work on 2019 Volt.

Most importantly... your equation for capacity is very wrong. What that PID actually returns is the Amp-Hour Capacity number times 10. So the correct equation is
(decimal representation of 2 last bytes) / 10
to get Amp-Hours. To get Watt-Hours from that, you need to multiply it by the "nominal voltage" of the pack. In order to arrive at that "divide by 30" you're using, that means that are using a nominal voltage of 333.333.
The correct value for gen-2 is 355.2. Please refer to the many important details here: 2015 Volt hanging tough without a garage
As you'll see in that thread, other multipliers need to be used for the various gen-1 years.
Because of the many inconsistencies of apps converting the car's Amp-Hours to Watt-hours, it's really a good idea to report both A-H and W-H so users can see what the conversion factor is.
Barry
 
#16 ·
Hi; I'm the creator of the MyVoltControl iOS app. Congratulations on your new app!

The things you are currently showing will also work just fine for gen-1 Volts (but with a few changes to your equations).
Note that the battery capacity PID you are using does not work on 2019 Volt.

Most importantly... your equation for capacity is very wrong. What that PID actually returns is the Amp-Hour Capacity number times 10. So the correct equation is
(decimal representation of 2 last bytes) / 10
to get Amp-Hours. To get Watt-Hours from that, you need to multiply it by the "nominal voltage" of the pack. In order to arrive at that "divide by 30" you're using, that means that are using a nominal voltage of 333.333.
The correct value for gen-2 is 355.2. Please refer to the many important details here: 2015 Volt hanging tough without a garage
As you'll see in that thread, other multipliers need to be used for the various gen-1 years.
Because of the many inconsistencies of apps converting the car's Amp-Hours to Watt-hours, it's really a good idea to report both A-H and W-H so users can see what the conversion factor is.
Barry
Hello, thank you so much, I will look into the thread for sure. Of course, I will consider the calculations that you have provided
 
#19 ·
Two things: Y
... which I dumped from the CarScanner app.
I wanted to mention that I'm pretty sure that all/most of the PIDs in Car Scanner came from this, so it's probably easier to get them from here: OBD2 and Vold PIDs for Android Torque in GoogleDoc

And I'm curious to know how you managed to dump a PID from Car Scanner. I've tried several times with no luck. I know there's an Export in Settings->Sensors but the export doesn't seem to contain anything useful. What's the trick? Thanks.
Barry
 
#20 ·
Two things: Y

I wanted to mention that I'm pretty sure that all/most of the PIDs in Car Scanner came from this, so it's probably easier to get them from here: OBD2 and Vold PIDs for Android Torque in GoogleDoc

And I'm curious to know how you managed to dump a PID from Car Scanner. I've tried several times with no luck. I know there's an Export in Settings->Sensors but the export doesn't seem to contain anything useful. What's the trick? Thanks.
Barry
it's under OBD2 adapter - export logs

 
#21 ·
#26 ·
v0.0.2 now launches correctly for me. I'll go out and test it against an OBDLink MX+ BT single on my 2013 soon.

Other side note, Play protect tried to block install of this app downloaded from GitHub. The reason was something like "Developer unknown". It did offer me the option to override that and install anyway, though.

Thanks, thx
 
#31 ·
v0.0.2 now launches correctly for me. I'll go out and test it against an OBDLink MX+ BT single on my 2013 soon.

Other side note, Play protect tried to block install of this app downloaded from GitHub. The reason was something like "Developer unknown". It did offer me the option to override that and install anyway, though.

Thanks, thx
I believe that's ok for apps from outside the Google Play.
Anyway, looking forward to seeing your test results as well
 
#28 ·
So I tried version 0.0.2 build 313 on my Note 9 running android 10, (2017 Volt) and it has minor issues. On the settings page, if you have a lot of bluetooth devices listed, the build and the send logs links are on top of the device I need to select (page needs to scroll), making that difficult. Also, capacity is only in amp hours and watt hours (not kW). Is there a way to change capacity to kW? History is not populating as well. Keep up the good work!
 
#29 ·
So I tried version 0.0.2 build 313 on my Note 9 running android 10, (2017 Volt) and it has minor issues. On the settings page, if you have a lot of bluetooth devices listed, the build and the send logs links are on top of the device I need to select (page needs to scroll), making that difficult. Also, capacity is only in amp hours and watt hours (not kW). Is there a way to change capacity to kW? History is not populating as well. Keep up the good work!
thanks for trying it out!
I will try to reproduce the issue with many devices and will make a fix. I will change the capacity units to kWh.
The history is under development. But the chart should show new points after new scans.
 
#36 ·
Thanks for the app update, it now launches on my S21 with OBDLink MX+ BT.
I like how you have added info for the section and group of cell when you select it.
Our vehicle is a 2019 so not sure about the Capacity values / per discussion above.

Another feature to add - the X-axis would be nice to have ticks for battery sections etc.
And / or the option to color the table columns a different color for each battery section.

Image
 
#37 ·
Thanks for the app update, it now launches on my S21 with OBDLink MX+ BT.
I like how you have added info for the section and group of cell when you select it.
Our vehicle is a 2019 so not sure about the Capacity values / per discussion above.

Another feature to add - the X-axis would be nice to have ticks for battery sections etc.
And / or the option to color the table columns a different color for each battery section.

View attachment 177460
Thanks for the feedback! I have been thinking the same about different colors of sections. Will definitely add this in next versions.
As for capacity values, this will be fixed too. I will need someone to test it so I will ask you if you don't mind
 
#39 ·
2018 CT6 2.0E plug-in with a cheap OBD-ll from ebay. It is charging on 8-amp wall charger.

View attachment 177485
Good to know it's working for you.
What is the screen of your phone, is it a small phone or you have just bigger text setting?
There will be an update soon that adjusts the UI for small phones
 
#42 ·
The new app version 372 (0.0.3) has been published to Google Play:
  • fixed capacity calculation for 2019 volt
  • added Internal Resistance & HV Isolation
  • UI & stability fixes

I would appreciate any feedback about this version.

P.S. Huge thanks to @BarryD for the suggestions
 
#45 ·
Worked great nice job and interface. Pixel 6 Pro. Android 13.

Images of yours and another for comparison of numbers. Car was not started.

Image


Image


Image

Image
 
#46 ·
Nice, thanks for sharing!
BTW, I notice some kind of "notch" in these 60-70 cells among other vehicles too. Does anyone knows the reason?
Here's mine:
Image