ABRP V4.2.0 with CarPlay and iPhone 11 Pro V15.4.
I drive an Opel Ampera-e with live OBD data via Torque Pro.
Our second vehicle is an Opel Corsa-e with OBD live data via ABRP Bluetooth OBD Connection. The OBD dongle of our Corsa-e is permanently live (this cannot be changed), the Bluetooth connection can be established at any time, but it only sends data when the vehicle is switched on. (Therefore there is no security problem ;-)).
Both vehicles are managed in the same ABRP Premium Account.
If I start the route planning for the Ampera-e by parking in the garage, it works until after a few meters I drive past our Corsa-e parked at the roadside of the property. Then the ABRP switches from the Ampera-e to the Corsa-e because it can establish a connection with the dongle. As a result, the SOC is displayed by the Corsa-e even though I'm driving the Ampera-e. The ABRP app then no longer automatically switches to the Ampera-e's Torque Pro connection when I'm out of range of the Corsa-e. The only remedy after I'm out of range of the Corsa-e is to manually select the correct vehicle, the Ampera-e, so that the route planning works properly again.
If I stay within range of the Corsa-e dongle with the Ampera-e, the ABRP app always switches from the selected Ampera-e to the Corsa-e after no more than 10 seconds, regardless of whether with or without navigation.
Maybe an ABRP OBD Bluetooth connection generally takes precedence over a Torque Pro connection, and that's why ABRP switches to the Corsa-e as soon as it sees it?
As a remedy, I suggest that as soon as the route planning has been started, the app must not try to connect to other vehicles stored in the ABRP account, but must stay with the selected vehicle.
What do you think?
ABRP v4.5.2 (2352)
With the last update unfortunately the problem appeared again: :-(
ABRP switches itself from Torque Pro to BLE live data connection during navigation!
BLE should NOT be the connection with the highest priority, especially if the car profile has an already established connection to Torque Pro live data and ABRP is in navigation mode!
In that case if I switch to the correct car during navigation, ABRP shows error on iPhone and says „could not route/find plan“). I have to open iPhone, click on X.
When I start the ABRP, there’s no routing and I stay within range of the Corsa-e dongle the ABRP app always switches from the selected Ampera-e to the Corsa-e. In this case the behavior is ok.
If I then switch to the Ampera-e, it remains selected, even if I am still within range of the Corsa-e. That's good!
With ABRP V4.2.5 (and maybe already since V4.2.4) I don‘t have any self-switching between the two cars. So the issue seems to be fixed.
Yes, it would be very useful to further improve this logic. :-)
I know that the Ampera-e can also use the ABRP OBD connection now. (It was me who made a request to expand the brand new ABRP OBD Connection ability of the Bolt EV to the sister model Opel Ampera-e.)
But I prefer using Torque Pro to observe further data like cell voltage, heating of battery and interior, and so on.
we have a logic, that does not switch anymore, when you connect two vehicles via our inbuilt OBD implementation. Looks like we should enhance that a bit more with other OBD input sources.
BTW the Ampera-e is also supported by our OBD implementation, so if you connect the Ampera-e with ABRP OBD, you should not see the switching anymore. Then we will just try to connect to the car that is selected.
With ABRP v4.2.6 it switches itself to the car with the OBDlink connection again. :-(
We did not fix your usecase yet. The fix was for two obd connected cars. This is still open for other combinations.
But it worked at times of ABRP V4.2.5 like written above, so I assumed a change had been made to my account.
Apparently it wasn't, and the fact that it worked for one version was coincidence ;-)