Marcad80
Well-Known Member
- First Name
- Marc
- Joined
- Nov 29, 2021
- Threads
- 10
- Messages
- 226
- Reaction score
- 273
- Location
- Florida
- Vehicles
- Model S
It could be, but I’ve worked with ASICs (application specific integrated circuits) for a long time, and most of the time a defect in a chip doesn’t result in another function being executed but a BiT(built in test) error. Or if no Bit is available, if a part of the chip goes bad it ends up creating a random signal that has no meaning at all and flags implausibility levels that shut down the function.Conjecture on my part but I think this problem isn’t software related. If it was Porsche would be all over it working on a download fix. Instead I think it’s likely a problem with chips controlling the park/neutral/drive functions - probably a bad batch of them which explains why not all Taycan owners are experiencing this problem, and further likely Porsche knows exactly what the problem is but can’t get its hands on enough replacements chips for a fix. And of course those chips are integrated on electronic controller boards so who knows how complicated/difficult a repair would be. But I don’t believe for a micro second that Porsche doesn’t know exactly the reasons and fix for this problem.
Kind of sucks having the excitement and joy of being a new Taycan owner tarnished by this sword of damacles hanging over our heads, wondering if/when we’ll experience it.
This is most likely a “corner” software case that their software design verification process didn’t consider. This I see a lot.
The problem is, if they are deep in a corner they are very hard to find in a test environment.
Sponsored