EVMan wrote:. . .
Its 2016 22KWH rex. I have the latest or close to the latest software , updated 3-4 months ago.
I updated mine last month. So far, no problems.
EVMan wrote:I can understand , it may be a software issue , but its a bigger safety issue.
They should replace the computer board , if required....
If anything like my local BMW shop, you're in good hands.
EVMan wrote:I am in Fremont CA, which has the maximum density of EV in the USA
But unfortunately , the dealer is not only of questionable character , but unquestionably , does not understand anything about software.
They only know hardware
Standard answers "We will do a software update and that will resolve the issue."
I understand the vehicle software is handled from Germany but I suspect something else has happened. Going back to the incident:
- Was the car running on the REx at the time?
- What did you code in the car?
- What coding tool did you use?
The reason I ask is some of the symptoms sound like the battery level was low. If the REx had come on following typical CARB initiated, low battery threshold levels, it might make sense. Last year, I was driving to Fayetteville and enabled the REx only to have a check engine light come on and the engine stop every time when I braked, accelerated, or even took a turn. It turns out the oil level was low and there is no oil pressure light. But I'd turned the engine on at 75% so turned around and drove to the dealer.
Except for tires, our BMW i3-REx needs a minimum of two days for any shop visit because parts and technical support come from out of state and sometimes Germany. Being a 2014, it has a risk of infantile problems. So when we had a motor mount 'bolt break in our 2014, I solved the backup car by replacing our perfectly fine, backup 2010 Prius with a new 2017 Prius Prime. Now both cars have dynamic cruise control and automatic, emergency braking.
Fear, uncertainty, and doubt (FUD), I can't do anything about it in others. But we can help with sharing our experience and insights.