Voters 30
-
-
J
-
C
-
M
-
-
-
O
- + 24 voters
-
-
U
-
J
-
J
-
M
-
D
-
J
-
-
-
C
-
-
A
-
D
-
-
-
2
-
S
-
H
-
K
-
A
-
-
M
-
N
Apple Maps EV Routing Support via SiriKit
- Investigate
- Subscribe
|
U |
UnnDunn |
Using SiriKit, iPhone apps can provide Siri with information about a car, including its battery SoC, maximum range and charging status. This information can be used by Apple Maps to provide EV routing information, which would be a good alternative to ABRP's routing information in certain situations.
Since ABRP can collect battery SoC and charging status information via OBD or through an online API, it would be nice if it could provide that information to Siri using SiriKit. This would provide iPhone users another routing option if ABRP's service is not available or not supported in a user's region.
More information about Car integration with SiriKit can be found here: developer.apple.com/documentation/sirikit/car_commands
Thank you.
Activity Newest / Oldest
Katya_ABRP
This ticket has been moved to our new feedback portal;
abrp.featurebase.app/p/apple-maps-ev-routing-support-via-sirikit-2
Steve Loughran
the apple api looks like a carplay feature which requires the car to provide the information-once that is done it should be possible for ABRP to ask for it fairly easily.
it does depend on the carplay/car integration. Apple have apparently demonstrated apple maps doing EV navigation with Porsche cars, so it is certainly possible-I just don't know the availability of the feature. and the car/phone power struggle gets in the way. Has anyone seen apple maps reporting vehicle charge status?
TheDago
Hi, I am not a coder, so I would not really know, but this sounds like using Tronity (which is supported by ABRP). So it should not be more difficult? also it would make things easier for us users, who would not have to pay for two services (ABRP and Tronity). Totally support this!
Katya_ABRP
Status changed to: Investigate
Katya_ABRP
Hi UnnDunn,
It's an interesting suggestion, but it does face some challenges;
1. ABRP can only read data via OBD over an active Bluetooth connection - which for iOS requires the ABRP app to be actively running.
2. OTA connections usually don't report data frequently enough to be reliable in navigation (but it can vary depending on manufacturer and connection type).
/Katya
Steve Loughran
One minimum would be “have ABRP pass the next destination to the car nav”. Apple Maps can do this to our BMW, and that’s all need: the car satnav can do its fancy HUD view etc, while ABRP can handle the problem of routing an EV -something they don’t seem that good at themselves. Nothing else, just “send next waypoint to car”
Jan
But if the situation changes, like traffic before the next charger, resulting in a different route with a different charger being faster overall? In this case the car‘s nav system would continue to route to the suboptimal charger nvertheless.
I think ABRP should have somethink like a guardian mode, just keeping the routing current with traffic and charger occupation, and let the car do the „tactical“ navigation to the next charger - because the cars navigation is better and also may heat the battery.
dlu
It seems like the car navigation would also need to accept "outside advice" and recognize the "next waypoint" as a charging stop. So, it seems like the car would need to support two or three messages:
1) next waypoint,
2) next waypoint is charging stop or these two could be combined into one message that both specifies the waypoint and tags it as a charging stop,
3) stop navigation (or some other way to say that we're no longer going to a charging station) or a way to substitute a new charging station as the current waypoint.
I suppose another approach would be to give the car's navigation system an ETA at the next charging station. Or, if there is a way to tell the car to start conditioning the battery that could be used at the expense of teaching ABRP how to manage the battery.