Based on Katya's recommendation
i'm creating a bug report here at Upvoty.
Three weeks ago I've 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 the ABRP App (V4.2.12 (1157)) 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, followed the instructions how to setup live data with TorquePro, but both configurations with their individual password also won‘t show me any live data in the ABRP App. Although the upload seems to work for these cars too. 🙃
(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 66kWh 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 api.iternio.com/1/tlm/torque the correct one, so meanwhile it's independent of car model? (In the past the GM Bolt had ../tlm/bolt60 and the Opel Ampera-e ../tlm/ampera60 as upload path to the ABRP Webserver).
Can someone have a look into my account, please?
The Instructions for live data endpoint are wrong:
Using ampera66 live data endpoint it works now for me.
There is no enhancement for this issue with the new website version ABRP V4.3.0 (1932) and iOS V4.3.0 (1930).
This looks solvable, we probably have not properly added the new Ampera-e to the Torque configuration.
Please also check the Bolt60/Bolt66 with Torque Pro configuration.
I‘ve had also problems getting a torque based live connection using them for counter test.
Unfortunately it still doesn’t work with Ampera66.
After going completely through the live data setup process, ABRP shows live data setup dialogs again.
I hope that I‘ve made no layer 8 error. ;-)
I‘ve recorded a short video clip to show you what happens:
I‘m no longer able to setup a new ampera60 with torque live data now, so it got worse than before. :-(
It’s the same broken behavior now like with the ampera66. I‘ve also tried to setup some of the various Chevrolet Bolt EV models with torque live data, they show the same issue: The torque pro connection is not retained.
Can you identify the cause from the video?