Planned SoC not what I expected

[Balloondoggle]

On a 90 mile drive I expected that the "Planned SoC" would indicate what the app expected the state of charge would be at a given point on the trip.  Instead, it read the initial live data state of charge and never changed.  If I forced a replan by tapping the button or straying from the planned route it would then update Planned SoC with the then-current live Soc.

Is there something wrong with my setup or did I misunderstand what Planned SoC is intended to convey?

I'm driving a '19 Bolt and get data to the app via Torque.  That all seems to work as expected and logs should be uploading to ABRP.

[Jason-ABRP]

Took a look at your data, and had a couple of thoughts:

First - your calibrated reference consumption is negative which will lead to very strange plans (like a plan where your planned SoC doesn't change).  Something's definitely wrong with our calculation there.  We'll look into it and see what we can do with that.  Until we figure out what's wrong, it's probably best to turn off the calibrated consumption feature for your car.

Second - the SoH PID is broken on the 2019's, and is giving a very strange value (14% of your battery capacity available).  You should probably disable that in Torque (and I'll add a note in the setup instructions)

[Balloondoggle]

Thanks Jason.  I've made the changes you recommend (I think - the closest I came to a SoH PID was battery capacity guess) but still got a negative calibrated reference consumption.  I've noticed that the app sometimes takes a while to acknowledge changes so I'll run it a few more cycles before I decide it's still broke.

Thanks for all the work you put in to this.  I've been working hard to understand it and get it set up for my car because we are planning a 1700mi trip this spring.  All the math and monitoring your app does gives me peace of mind I won't get from basic Plugshare charger locations.

 

Separately, I've spent a lot of time trying to understand the terminology and what all the information means, and it's been a bit of a struggle for me.  As an example, I thought the negative calibrated reference consumption was simply my measured departure from the standard.  I guess that was a bad assumption....  If there's any interest in developing a "quickstart" sort of guide for newbies I wouldn't mind volunteering to be involved in that.  Or it it already exists, where might I find it?

[Jason-ABRP]

We definitely want a quickstart guide! Once we're pretty happy on the UI we'll put out some videos going over the app and how to use it.

For calibration, it's really just the app learning your driving, and it'll learn in the background whenever you feed it data.  The most important takeaway is that it's a full car model, at all speeds.  So you need to feed it data at all speeds, otherwise it has to make some guesses (and weird ones sometimes!).

Have you driven with Torque sending data in at a range of speeds yet? Maybe spend a few minutes at 35, few minutes at 55, and a few at 75 to give it some good data to work with.

Finally, while it's learning, you can disable the calibrated consumption by clicking the blue car icon next to Reference Consumption in the plan settings:

And then once it's got a reasonable calibration (closer to what you'd expect from your car) re-enable it.

[acrollet]

Hi there, hope it's ok to chime in on this thread. I have a 2020 bolt and I'm trying to get live data working with Torque Pro - I got the connection established and ABRP shows speed, but no other data. It also shows the message 'Missing telemetry: soc, is_charging,' Also, the native app is showing a blank white screen on both android and iOS. (On the plus side, now I have another flashlight app ) I followed the instructions in the app for which PIDs to send to the server... Anything I could try?

[Jason-ABRP]

Just added those instructions for the 2020 Bolt to the server last night, glad someone's giving them a try! (If not, could you run through the 2020 Bolt instructions on the app under "Add My Car" and make sure they work right?)

If those instructions don't work, here's some things we can double check:

• Create a display in Torque and make sure it's getting good values from the car for SoC
• Screenshot the PIDs you have selected for logging, I can sanity check you make sure those are the same ones I'm expecting to receive
• Go for a short drive, sometimes the Bolt reports odd values when parked for some parameters.

[acrollet]

Hi Jason,

thanks for the response! Unfortunately I can't re-access the instructions in the app since it's only giving me a white screen. I tried looking in the website version but no luck so far. Which exact PID should I be using for SoC? I have a SoC raw and a SoC HD raw, also the SoC DIC value. I did take a drive this morning and am able to see updated values for km/h, but nothing else has changed.

[Jason-ABRP]

Can you delete and re-add the car?  Will require that you update the token in Torque.

Here's what I have selected in Torque for the web logging:

[acrollet]

Hi Jason, thanks again for the response - is there a way to delete and re-add from the webapp? (Since the native app doesn't work) I did adjust the PIDs sent to match your screenshot and took a drive, no improvement though.

[Jason-ABRP]

Hmm, took a look at your data on the server, and it seems like you're missing the State of Charge and Charger Power PIDs, which is crashing the app display for live data.  We'll fix the crash on our side, but I bet if we resolve that on Torque we can get it working.

Can you double check you're sending in these PIDs:

• !Battery Level Displayed (PID 228334)
• !Charger HV Power (PID ed22ae)

The PID number actually matters here as that's how Torque formats it to send to ABRP, so if you have a different but similar-sounding PID selected it could be causing problems.

[acrollet]

Hmm, that’s really odd. I just verified the PIDs and even cleared and reselected them with the same result. Here’s what I have:

 

 

[acrollet]

Also verified that torque pro is reading values for those PIDs:

 

 

[TomTomZoe]

On 3/5/2020 at 6:08 AM, acrollet said:

Hi there, hope it's ok to chime in on this thread. I have a 2020 bolt and I'm trying to get live data working with Torque Pro - I got the connection established and ABRP shows speed, but no other data. It also shows the message 'Missing telemetry: soc, is_charging,' Also, the native app is showing a blank white screen on both android and iOS. (On the plus side, now I have another flashlight app ) I followed the instructions in the app for which PIDs to send to the server... Anything I could try?

I‘m driving an Ampera-e 2018 and I also have the same  ‚missing telemetry’ issue and the ‚white screen’ issue, but no solution at the moment.

Edited March 6, 2020 by TomTomZoe

[TomTomZoe]

On 3/5/2020 at 5:58 PM, acrollet said:

Hi Jason,

thanks for the response! Unfortunately I can't re-access the instructions in the app since it's only giving me a white screen. I tried looking in the website version but no luck so far. Which exact PID should I be using for SoC? I have a SoC raw and a SoC HD raw, also the SoC DIC value. I did take a drive this morning and am able to see updated values for km/h, but nothing else has changed.

Try to uninstall and reinstall the app, then you should be able to start it without white screen hangup.

Log into your account and use it, but do not restart the app.
If you restart the app in logged in condition it will crash, at least on both off my iOS devices.

Edited March 6, 2020 by TomTomZoe

[Jason-ABRP]

I tried replicating the issue once again on my end, but to no success.  I've reset your data on the server, and have added some additional logging to try to catch whatever error is causing problems for @TomTomZoe and @acrollet.  Could you guys go for a drive while logging with Torque, see if we can trigger the error once again?

[TomTomZoe]

 

@Jason (ABRP)

Attached my PID settings for web upload and the webserver upload URL.

The "!Battery Level Displayed" PID is "SOC Display" on my Dashboard.

This afternoon I will go through abrp live data setup once more, use the new passcode for Torque Pro and will drive some minutes while uploading data.

Edited March 8, 2020 by TomTomZoe

[TomTomZoe]

These are my data recording and upload settings, I hope they are correct concering ABRP.

The web logging interval is set to 5 seconds.

Edited March 8, 2020 by TomTomZoe

[TomTomZoe]

I found out how to change Torque Pro's language to english

 

[TomTomZoe]

Thank you very much for resetting my personal data@Jason (ABRP)

I just drove about 7 minutes. I saw that the age counter began to count starting with 0:00 now, but unfortunality it still got no update and no values.

I will send you the corresponding logfile by PN, so you can compare if data is transmitted in general to your webserver and which values are damaged or missing.

Like meantioned before, neither the app nor the new website are running in logged in condition, only the old website is starting but still showing the error "Missing telemetry; soc_power, is_charging".

Edited March 8, 2020 by TomTomZoe

[TomTomZoe]

@Jason (ABRP)Maybe we treat this topic better in the "Live data not showing" thread? I think that others who have the same problem can find it better there.

Edited March 8, 2020 by TomTomZoe

[Justin]

So I'm also having issues with my 2017 Chevy Bolt and SoC.  The PID that's in the instructions ( !Battery Level Displayed) doesn't return any data for me.  However I found a PID (!State of Charge Raw) that seems to have the actual battery level.  I'm not sure how to make Torque return that correct PID value as  (!Battery Level Displayed).  I know it might be a lot of work on the backend side but a more generic Torque logging endpoint that lets you pick PIDs that match the required fields might be helpful, even if it is just to help debug setups.

.

[TomTomZoe]

@Justin

I used to have the same problem that not all PIDs show a value when I'm building a dashboard for Torque Pro. Make sure that the vehicle is switched on. Try to scroll up, wait some seconds, scroll down, wait same seconds. In my case the missing values were then displayed. If this doesn't help try another type of OBD dongle, there are some which are not able to query all PIDs.

If against all odds this doesn't help, which I don't think it will, then you can edit the Bolt's PIDs (csv textfile) and
- change the name of the original "!Battery Level Displayed" e.g. to "*Battery Level Displayed" (line 25)
- rename the text "!State of Charge Raw" to "!Battery Level Displayed" (line 21)
- reimport the modified PID csv textfile and overwrite all existing PIDs.
Be carefull: Many editors change linefeed, newline, spaces, tabs, encondig and so on. For Torque Pro, no changes must occur in this respect, otherwise it cannot use the PIDs. If you use Notepad++ for example you are safe.

For your information:
- "State of Charge Raw" is SOC in relation to gross capacity. In my Torque Dashboard it's named "SoC Real".
- "#State of Charge Usable" is my own net calculation of SOC. This is a calculated value of the SOC taking into account 3.9% non-usable buffer in the lower and upper gross SOC range. In my Torque Dashboard it's named "SoC Usable".
- "!Battery Level Displayed" is SOC which is viewable in bolt dashboard. It is about 99% of the useable SOC. In my Torque Dashboard it's named "SoC Display".

 

 

Edited March 11, 2020 by TomTomZoe

[TomTomZoe]

22 minutes ago, TomTomZoe said:

@Justin

- change the name of the original "!Battery Level Displayed" e.g. to "*Battery Level Displayed" (line 25)
- rename the text "!State of Charge Raw" to "!Battery Level Displayed" (line 21)

If I know this correctly Torque Pro distinguishes PIDs by the long name of the PID. Therefore an adaptation of the identifier "Name" (column A) should help.

Edited March 11, 2020 by TomTomZoe

[Jason-ABRP]

Actually, turns out the Bolt doesn't actually have a 4% battery buffer, the "Actual SoC" or "Raw SoC" measurement is against a hypothetical maximum voltage of 4.20V which the cells aren't actually capable of reaching:
https://allev.info/2019/02/bolt-battery-buffer/

Torque Pro does distinguish by long name, but it logs them to the server by k+PID, so I can really only use the one PID without making some substantive changes to the receiving server code.

If you're interested in a little more robust of a solution, I've got two options I've been working on (slowly, among all my other projects).  I've written some code for the AutoPi, which would allow for a nice standalone device (always get SoC and other updates even if you're not near the car):

https://github.com/iternio/autopi-link

And I bought a Freematics One for a cheaper solution, but haven't had time to write the code for it yet:

https://freematics.com/store/index.php?route=product/product&product_id=86

Both of these would make for really solid solutions that wouldn't require leaving a phone in the car to get remote data while charging.  And both would allow some customization of capabilities, like picking a different SoC PID, or voltage PIDs depending on what's available.  I'd be happy to help anyone interested in putting some work in on building out one of these solutions.

[Justin]

Awesome, with that info I might send all the raw data to my Home Assistant (https://home-assistant.io/) Instance since I wanted to get the data there anyway.  I have a spare phone I planned on just leaving in the car anyway, Google Fi is nice for data sims and I just need to pay for data used.  Once it's in Home Assistant I can send it to the API for ABRP in the correct format.  The autopi looks sweet, but I don't think I can justify the cost.  Might look into the freematics, would need to dust off my C skills though.