Kelpie_automotive
Member
- First Name
- Scott
- Joined
- Apr 15, 2021
- Threads
- 0
- Messages
- 19
- Reaction score
- 22
- Location
- Norway
- Vehicles
- Taycan 4S PBP
I have the exact same problem and it started when BMS surveillance SW were implemented. This is what I feared would happen. I’ve seen similar issues with computers and phones.
Bottom line, we paid serious money for a car that has the hardware of a 10 year old computer. What’s worse is that even as far back as 10 years ago the hardware would still be mediocre at best.
Bottom line, we paid serious money for a car that has the hardware of a 10 year old computer. What’s worse is that even as far back as 10 years ago the hardware would still be mediocre at best.
The specialist at my Porsche center diagnosed the issue as a RAM problem. The problem arises because backend changes and OTA updates alter the API responses. Consequently, more map data, including charging information and traffic hazards, is sent to the PCM, which is now handling a larger volume of data. This overload causes the PCM to crash. To mitigate this, the specialist recommends turning off the Charging Planner to reduce the size of the responses and turning off the satellite view to free up memory.
While these measures provide a temporary solution, they are not a permanent fix. The OTA update for the BMS is too busy managing data, and they either need to revert the changes or update us to a new build of the navigation app.
The fact that Skoda and Audi forums describe the same problem confirms this expectation. The backend is providing excessive data. This also explains why it’s an EU-specific issue. In the EU, there’s likely a vendor for that data that’s sharing too much information. For instance, a charging point supplier that shares too much data (in bytes) can cause VOWA navigation systems to crash.
Sponsored