Recent content by zwede

I've replaced it twice in my 2013. Wouldn't call it fun but it's not a big deal. A few cuss words and evil thoughts about the Tesla engineer who put it there and then I get it done.

Back before Tesla was forced to replace the eMMC boards for free Gruber offered an eMMC repair service. You had to remove the MCU yourself, then remove the eMMC board and mail it to Gruber. They would attempt to read the contents and put it on a new chip. If they couldn't read it they would put...

Yes, new instead of reman. Paid $19k with tax or actually $18,800 after credit card cash back. It charged to 267 miles at 90% so a little shy of 300 miles at 100% I guess.

Update on my new 90kWh battery: Did my first SC to see what charge speeds it has. Charged from 75 miles range to 210 and saw double the kW throughout the charging session compared to the old 85 kWh battery. Got 118 kW at 75 miles and still over 100 kW at 130 miles. Charging was still free as...

Yeah, that's me. My experience is the service advisors at the SC are remarkable clueless. The first one I talked to called California and then told me ALL replacement packs are brand new even if they say reman on them. When I expressed doubt he dug in. He had just talked to the experts and was...

Only 39k miles. Seems this fault is triggered more by time than mileage.

Nice! Definitely looking forward to those charge speeds!

My new pack is scheduled to be installed end of next week. My old pack would max a 72 kWh urban SuC until 135 miles of range when new. After charge gate I see about 60 kWh at 70 miles of range and in the 40's at 135 miles. I'd expect the new pack to at least match what I had before charge gate.

I tried accessing the google doc before I was approved in FB so that explains it. I got the doc now. Thanks.

I mention estimated range right at the end of the post.

I get "Access Denied"?

My 2013 P85+ got the infamous bms_u029 "Charge level reduced" last week and after reading up on the forum and going back and forth with Tesla Service I decided to write up what I learned. Much of this info is available on this forum but buried in various threads. My hope is to make this post...

That's a weakness in how Tesla implemented this. The actual nav data is on the SD card, but the information of what is on the card is stored on the main storage drive (eMMC). So now you have the situation that the MCU thinks it has maps but when it tries to access them on your new SD card...

Yes, that is odd. Mine had 2x 8 GB partitions with squashfs file systems. One partition was OK and the second heavily corrupted due to the card failing. Maybe your card has failed to the point you don't even see partitions. My understanding is that if you're not due for a map update it won't...

You can probably do 2x 16 GB but it doesn't make a difference, only 2x 8GB will be used. Maps are in the squashfs file format which is a compressed read-only format. Once maps are deployed on the card they will always be in a 8 GB image.