PDAZ
Member
- First Name
- Alexander
- Joined
- Apr 26, 2025
- Threads
- 1
- Messages
- 24
- Reaction score
- 5
- Location
- Koenigstein im Taunus
- Vehicles
- Porsche Taycan 4S Cross Turismo
- Thread starter
- #1
Hi all,
I’ve been driving a Taycan for quite some time now and recently ran into a problem again that I believe many of you will recognize – and frankly, it’s starting to get really frustrating.
The issue is not the charging hardware. The Taycan is technically capable of extremely fast charging.
The issue is getting the battery into the right temperature window at the right time.
The real-world problem
I’ve now had multiple situations where:
Simply because the battery wasn’t properly preconditioned.
The root cause seems obvious:
→ Preconditioning only reliably works when using the Porsche navigation system with a charger set as destination.
What makes this worse in practice
Many of us don’t actually use the Porsche navigation system:
→ the car does NOT precondition the battery
Additionally:
Result:
→ You lose a massive amount of charging performance purely due to software limitations
The idea
I’m seriously considering building a small iOS app (I have my own Apple Developer account and can build and publish apps), with the following concept:
→ Trigger preconditioning indirectly by sending a nearby HPC as a “dummy destination”
Proposed functionality (MVP)
From my experience:
That’s essentially double the charging time.
And the frustrating part:
→ This is not a hardware limitation – it’s a software/UX gap.
Current observations
→ The building blocks exist, but aren’t connected
Questions to the community
This could be a simple but high-impact tool
Closing thought
I really like the Taycan – but this is one of those cases where:
→ software is clearly holding back the hardware
If this gap can be closed even partially, it would make a noticeable difference in real-world usability.
Happy to share progress if I move forward with a prototype.
Curious to hear your thoughts.
I’ve been driving a Taycan for quite some time now and recently ran into a problem again that I believe many of you will recognize – and frankly, it’s starting to get really frustrating.
The issue is not the charging hardware. The Taycan is technically capable of extremely fast charging.
The issue is getting the battery into the right temperature window at the right time.
The real-world problem
I’ve now had multiple situations where:
- I arrived at a 300 kW charger (Aral pulse / Ionity)
- battery SOC was low (even around ~5–10%)
- but charging power still stayed around ~100 kW (sometimes even less)
Simply because the battery wasn’t properly preconditioned.
The root cause seems obvious:
→ Preconditioning only reliably works when using the Porsche navigation system with a charger set as destination.
What makes this worse in practice
Many of us don’t actually use the Porsche navigation system:
- CarPlay / Google Maps / ABRP
- external route planning
- spontaneous charger selection
→ the car does NOT precondition the battery
Additionally:
- selecting a charger 5–10 km before arrival is too late
- “send to vehicle” via Porsche app is unreliable
Result:
→ You lose a massive amount of charging performance purely due to software limitations
The idea
I’m seriously considering building a small iOS app (I have my own Apple Developer account and can build and publish apps), with the following concept:
→ Trigger preconditioning indirectly by sending a nearby HPC as a “dummy destination”
Proposed functionality (MVP)
- User logs in with Porsche account
- App retrieves vehicle + location
- App finds HPC chargers within ~20–40 km radius
- User taps: “Precondition battery”
- App sends selected HPC as destination to the vehicle
- Optional: retry + status/confirmation
- No direct battery control
- Only using existing Porsche navigation logic
- Automates what we already try manually
From my experience:
- Proper preconditioning → ~250+ kW
- No preconditioning → ~100 kW
That’s essentially double the charging time.
And the frustrating part:
→ This is not a hardware limitation – it’s a software/UX gap.
Current observations
- ABRP has Porsche integration (live data), but does NOT push destinations
- Porsche app can send destinations, but unreliable
- Projects like Porsche EV Insights show API access is possible
→ The building blocks exist, but aren’t connected
Questions to the community
- Has anyone already built something like this?
- Is there any known API endpoint for sending navigation destinations reliably?
- Has anyone experimented with automating “send to vehicle”?
- Any known pitfalls beyond reliability?
- Would you actually use something like this?
My hypothesis
This could be a simple but high-impact tool
- uses existing vehicle logic
- solves a real everyday problem
- especially relevant for CarPlay / external navigation users
Closing thought
I really like the Taycan – but this is one of those cases where:
→ software is clearly holding back the hardware
If this gap can be closed even partially, it would make a noticeable difference in real-world usability.
Happy to share progress if I move forward with a prototype.
Curious to hear your thoughts.
Sponsored