Live Data values are no longer being updated although Torque Pro Status is connected

[TomTomZoe]

I'm driving an Opel Ampera-e 2018. ABRP gets OBD data from Torque Pro through Webserver Upload. Torque Pro adapter status shows regular successfull uploading of OBD data.

Since two or three weeks I have the problem that the Live Data values are not beeing updated although Torque Pro Status is connected.

Although the live data status says "connected" in CarPlay and the corresponding bar icon is green (and not red), the live SOC is not updated. The routing always starts (in my case) with 62% SOC, although it is configured to use live SOC. Please see screenshot.

I didn't change anything significant in the OBD setup for months.
The only thing that comes to mind is that about two or three weeks ago I appended the additional PIDs for the future 65kWh HV replacement battery as additional lines to the PID file at the end and then imported the expanded PID file into Torque Pro overwriting them. As a result the new PIDs in Torque Pro were useable.

To rule out a possible negative impact of the additional PIDs, I completely deleted the PID configuration from Torque Pro and read in the original old PID file again. The Live SOC then worked again once, after that it stopped working again. Very strange.

Maybe it has something to do with the fact that ABRP App can use OBD dongles now directly instead of being dependent on web server upload since some weeks?

Some minutes ago I had a closer look on the transferred data: Not only the SOC, but also both temperatures, the voltage, the current and so on are outdated, although it is connected. The time of the last update is continuously counted up, so the ABRP App seems to receive data.

@Jason-ABRP Is there again a problem with my car configuration in the ABRP database like it was approx. 2 years ago?
Can you please help me by finding the root cause for the actual issue? If you need any additional information from me, please tell me.

Edited January 17, 2022 by TomTomZoe

[Jason-ABRP]

I don't think we made any recent changes to the Torque receiver, so I expect it should still work.  Unfortunately I don't have access to a car anymore I can test with Torque, (Chevrolet bought back my Bolt EV as part of the battery recall, and I ended up replacing it with an ID.4).  

That said, I tried sending in some data formatted like Torque sends from a Bolt EV / Ampera-E, and it seemed to work as expected.  In Torque are you seeing different values than what is shown in ABRP? I do know that the battery upgrade doesn't change your PIDs, if you were using the 2017-2018 PIDs before, you'll continue using those.

As far as what to try next, once you confirm that you're seeing the different values in Torque, I'll enable some extra logging and see if we can pinpoint the issue.

[TomTomZoe]

Yes of course, Torque Pro always shows me the actual values. 
Last year ABRP live data worked fine, since the first usage in this year I have the problems.

I had a look at the actual required PIDs and saw that these have changed now compared to the original setup I made years ago. Now it requires one of two different „estimated kWh“ values, two years ago it required a PID called „battery capacity“. I don‘t know the exact name of the three PIDs at the moment, my Android Tablett is in the car at the moment. It also requires now an Charge Port Amp PID, formerly the PIDs name was without ‚Port‘

Is it possible that the calculation meanwhile uses only one of the two new capacity PID names and no longer the old name?

Since two, three days I added all capacity PIDs and most of all other  changed PID names for logging and upload. I will test tomorrow or Monday if it still doesn‘t work.

If the required PIDs may have changed months ago, I don’t understand why it worked with the old PIDs for me till last month without any problems.

Edited January 22, 2022 by TomTomZoe

[TomTomZoe]

At the moment it is transfering data via OBD Torque Pro Upload and the ABRP App is receiving nearly all data, strange but I'm happy

Unfortunately the Battery capacity (or degradation) is not shown in ABRP App, although "!Battery Capacity" PID is shown in Torque Pro and also used for Upload to ABRP Webserver.

@Jason-ABRP
The available Torque Pro PIDs are:
!Battery Capacity,Capacity,2241A3,((A*256)+B)/30,0,65,kWh,7E4 -> I've used this PID since beginning without problems.
!Battery - Pack - Capacity kWh estimated 2017-2018,Bat Cap Est,2241A3,((A*256)+B)*0.032,30,70,kWh,7E4 -> Since MY2019 exists, slightly different conversion for MY2017-2018
!Battery - Pack - Capacity kWh estimated 2019+,Bat Cap Est,2245F9,((A*256)+B)*0.0032,30,70,kWh,7E4 -> New PID for MY2020+

I added "!Battery - Pack - Capacity kWh estimated 2017-2018" PID in the logging for testing purposes, but with no effort on the ABRP Capacity display.

Can you imagine what the reason for this is? In former versions of the ABRP App the Capacity was shown. Or is it a matter of the two new Capacity PIDs ("!Battery - Pack - Capacity kWh estimated 2017-2018" and "!Battery - Pack - Capacity kWh estimated 2019+")? Can you confirm that "!Battery Capacity" PID is still used from ABRP?

Incidentally, is the initial car temperature the ambient temperature?

Edited January 25, 2022 by TomTomZoe

[TomTomZoe]

Jason, you may also add OBD Direct connection for Opel Ampera-e? You know they are identical to GM Bolt EVs which can use this feature already.

 

By the way: The ABRP Website shows a battery degradation (with the standard value of 5%), instead of the battery capacity.

Edited January 25, 2022 by TomTomZoe

[Jason-ABRP]

@TomTomZoe - I've updated the support files, so you should see both Torque and OBD BLE available for the updated Ampera now, and I went through and compared all the PIDs I expect to receive for the Ampera with your logging PIDs.  As long as "ampera" is in the name of the car model (which it is for all versions of the Ampera-E) it gets parsed using:

"current": 	"222414",  # A
"voltage": 	"222885",  # V
"power":    	"e16f08",  # kW
"soc":      	"228334",  # %
"capacity":     "2241a3",  # kWh
"alt_capacity": "2245f9",  # kWh
"ext_temp": 	"220046",  # *F/*C
"alt_ext_temp": "22801f",  # *F/*C
"batt_temp": 	"22434f",  # *F/*C
"speed": 	"22000d",  # kmh/mph
"is_charging": 	"22436c",  # amps
"alt_is_charging": "ed22ae",  # kW
"is_dcfc": 	"224424",  # amps

Where the 'alts' are variations between the two PID sets of the Bolt EVs.  

Also, you are correct, we assume your car is cold-soaked, so the initial temperature is the external temperature.  It's to add a transient power draw for a few miles after starting a drive, to account for that in the calibrated consumption.

[TomTomZoe]

@Jason-ABRP

On 1/25/2022 at 9:22 PM, TomTomZoe said:

By the way: The ABRP Website shows a battery degradation (with the standard value of 5%), instead of the battery capacity.

 

The App V4.1.14 shows no capacity or degradation for the Ampera-e.

 

The Website V4.1.15 shows the capacity:

 

 

 

@Jason-ABRP

Does this mean this issue is fixed also with App V4.1.15?

 

Edited February 6, 2022 by TomTomZoe

[TomTomZoe]

Just updated to App V4.1.15, but this version also shows no battery capacity for Ampera-e. So it seems to be a bug of the App.

Edited February 6, 2022 by TomTomZoe

[Jason-ABRP]

Ah, capacity and degradation are mutually exclusive values, if you have one, you can't have the other.  If you have a live data source of capacity, we'll use that in planning (thus why it shows up in the settings list).  If you don't, you can specify a degradation % and plan using that value.  

[TomTomZoe]

The capacity value is transfered via Live Data to the ABRP Webserver. The value is used for routing. Check.

@Jason-ABRP

But I still don‘t understand why the website shows the last live value, but the App shows no capacity value at all. Why is there a difference? Is this intended?

 

Edited February 28, 2022 by TomTomZoe

[Jason-ABRP]

Ah, understand.  Missed that the app was the one misbehaving.  I'll send you a PM on this one.

[Jason-ABRP]

Also, since the capacity is associated with your vehicle, it's definitely being used in planning whether it's shown in the app settings or not.  The planner pulls the vehicle data separately from the app, so it should be purely a display issue.

[TomTomZoe]

Yes, it is only a display issue.

Edited February 28, 2022 by TomTomZoe

[TomTomZoe]

@Jason-ABRP

Last week I got the new battery with higher capacity for my Opel Ampera-e. 

ABRP works still with the same TorquePro Upload and the driver model named Ampera-e (upload path …/ampera60).

Due to there‘s a better driving model for the battery upgraded cars, I’ve set up a new car in my profile: A „Opel Ampera-e with 66kWh Upgrade“. I clicked through the instruction to configure Torque Pro and saw that the upload path is not …/ampera66 like I thought but …/torque.

I configured TorquePro with the new password and the new upload path ../torque and it seems that Torque Pro can upload data successfully (there‘s no data waiting for upload), but ABRP still shows no green Livedata Icon and no live data at all. Beneath “Edit settings” ABRP shows “Live data”. When I click on the Live data button, the instructions to configure live data appear again, even I‘ve gone through these steps already. 

For testing I also tried to setup new cars based on the Bolt EV 66kWh and Bolt EV 60kWh, but both configurations with their individual password also won‘t show me any live data in ABRP.

(I want to stay using TorquePro if possible, to be able to see also battery cell voltage and temperatures, so OBD BLE direct with ABRP is no real option for me at the moment )

 

The formerly used Ampera60 configuration is still working with the new battery, but I think it would be better for correct planning to use a car configuration with the 65kWh ABRP driving model? The charging curve is also modified by GM.

What do you think about it?

Did I made something wrong while configuring a new car with live data?

Is the upload path http://api.iternio.com/1/tlm/torque the correct one, so meanwhile it is idependent of car model? (In the past Bolt had ../tlm/bolt60 and Ampera-e had ../tlm/ampera60 as upload path).

Can you have a look into my account, please?

This Friday tilI Sunday I will make a long trip, so it would be very helpful for me if I could use the 65kWh driving model.

Thank you very much for your help.

Edited October 5, 2022 by TomTomZoe

[TomTomZoe]

In the second part of my writing aboth replace 65kWh by 66kWh. 

[TomTomZoe]

Maybe @Samuel-ABRP is able to have a look into it.

[TomTomZoe]

The long trip is over.

Or @Bo-ABRP, can you please take care of this topic above?

 

At the moment I'm feeding the ABRP 60kWh Bolt/Ampera-e car model with the live data of my 66kWh battery. I don't think this is optimal for the 60kWh ABRP car model.

 

Edited October 9, 2022 by TomTomZoe

[Katya-ABRP]

Hi @TomTomZoe,

There shouldn't be any issues with linking the new vehicle copy via Torque pro (we haven't made any changes that could've affected it). If you're still experiencing issues with linking the new vehicle copy, would you mind submitting this as a bug report in Upvoty? Any pieces of obd data you think is missing or could be better displayed for you could also be submitted as feature requests. (This forum is otherwise only meant for discussion among users themselves these days).

/Katya

[TomTomZoe]

@Katya-ABRP

Apparently the actual issue seems to affect only my own personal account and not all users, so on monday I sent Jason a PM about this issue, which unfortunately hasn't been answered yet.

 

I've just created an request:

https://abrp.upvoty.com/b/report-a-bug/linking-obd-to-new-car-models-not-possible/

Edited October 20, 2022 by TomTomZoe