Hello TMC forum, it's been awhile since I've posted but I've run into an issue that I've basically lost faith in Tesla Service to solve, and hoping someone in the community might have seen this and/or has some troubleshooting ideas.
Problem: The instrument cluster reboots (goes blank, then shows the many fault-icons that we see when we first get in the car and step on the brake, all while showing the side-view image of the car), and it happens usually in the first 1-4 minutes of trip-time after getting in the car (happens while in Park, in Drive but stopped, while driving, basically in any condition you can imagine. This reboot would typically only happen once in the beginning of the drive, but I think I have seen it maybe more than once in a drive. But I'd say 90% of the time just once in the beginning of the drive.
Car information: December 2016, P100D Model S, just under 35K miles (still under warranty), originally Autopilot 2.0, but in late July was upgraded to FSD AP computer with purchase of FSD, AND had the MCU2 (with the associated new IC) installed. (oh, and with my new MCU installation, when the car was returned to me after service it had a prominent yellow border around the screen. My original MCU touch screen never had a yellow border to begin with! But that's just adding to my frustrating service story... I had it replaced and new touch screen is fine, but pretty unbelievable none the less).
(READ ON FOR MORE DETAILS IF YOU'RE INTERESTED BUT THE ABOVE INFO SHOULD SUFFICE FOR ANYONE THAT WANTS TO REPY)
More information:
Service Center- Centinela (Los Angeles)
So the variables go up from here... Around the time I had the new MCU installed, I began using the Teslacam feature with a USB stick, and shortly after that purchased a SAMSUNG T5 Portable SSD 500GB - Up to 540MB/s - USB 3.1 External Solid State Drive, Black (MU-PA500B/AM) from Amazon and began using that for my Teslacam. This comes into play later...
History of issues (perhaps some of these other issues are related?):
I had multiple issue after my MCU replacement in July. I not only had the IC reboot happening often (I didn't keep track at first, I had more pressing issues), I was having bigger problems with the AP visualization. On nearly every drive I had my repeater cameras (the two on the side that look rearward and are part of the backup camera visualization and Teslacam recording) blank out, just go black, and usually caused a message that said autopilot features unavailable and the IC visualization of cars, signs, road markings, etc would just disappear, usually not returning until after the car was parked for a period of time. Ugh. I also began having issues with the backup camera not saving to the Teslacam, even tho the backup camera continued to work fine, but not a huge deal.
I had to go back into Tesla about replacing the touch screen (oh and they forgot to reattach a wiring plug so my hazards didn't work for awhile after I first got my car back from the MCU2 install), and then back again for the autopilot/ visualization issues, rear camera not saving from Teslacam, and IC reboot. They claimed all 3 were fixed, and true enough the AP/visualization and the rear camera saving to drive issues were resolved but the IC reboots continued. I give credit to the service advisor that made an appointment to come back in without me even requesting it when I told him the IC was still rebooting, but I was just happy the other two issues were resolved, the IC I guess I can live with as it doesn't really interfere with driving or even AP use (tho just today I discovered that when on a phone call using BT through the car, the call is hung up, so now I am annoyed with this to the point where I'm writing this on the forums!).
I came into service now for the 4th time since the MCU2 installation upgrade, the issue was traced by the service technicians/engineers to a corrupted SSD, my Samsung I mentioned above. I had already tried re-formatting the drive many times myself as a troubleshooting idea, but they claimed that was the source of the reboots and when disconnected the IC reboots didn't occur. I took their word for it, received the car back, and stopped using the Teslacam all together. Well, sure enough, the problem happened again days later, and I even recorded it happening without the drive connected. Oh, and to add salt to the wound, the hazards weren't working again after getting my car back from service.
At this point I was pleased to hear that the Service Center agreed with me that the best course of action was to try replacing the entire IC. They sent Mobile Service to me but it turned out they had the wrong IC... Awesome. At least they reconnected the wiring for the hazards. Well, now they wanted the car back at the SC so they could do it properly, so I brought the car in that day. Apparently after they replaced the IC, the rebooting continued so they decided to order a whole new MCU2 (and IC) upgrade package.
After getting the car back a week later with the new IC and MCU2, I was told that maybe just to be safe I should try not using the Samsung SSD for awhile just as a baseline, they still believed it was the culprit or related to the reboots. I agreed and drove off using a simple USB Thumb drive (I really like using the Teslacam as a precaution just in case I need the footage if something happens to my car while driving!). The next day I had a reboot again at the beginning of the drive. Back to the drawing board. I haven't contacted Tesla and not sure I will as they just don't seem to have a handle on this issue and I'm apparently the first case, lucky me. Oh, and the right USB port was no longer powered after they returned the car to me, I had to go back for the 6th time since the original MCU2 upgrade to have them fix it... Now it's fixed.
I began using the SSD again because why not, the reboots are still happening no matter what I do. I even reformatted it again just in case, and I'm consistently getting reboots in the first 1-4 minutes of driving. I began experimenting with beginning my drive with it unplugged and then plugging in after a few minutes into my drive, and perhaps it's my imagination but seems like the reboots aren't happening as much, so perhaps there is something to the SSD affecting the reboots of the IC. I need to collect more data on this but I still suspect it's something else, just from the fact that the reboots have happened with the SSD completely unplugged from beginning to end of some of my driving trips.
For anyone that's read this far, wow, greatly appreciated... I know it's a lot of info and details but this is a weird issue that I'd like to resolve, so thank you for reading and any suggestions or info you have to share!
Problem: The instrument cluster reboots (goes blank, then shows the many fault-icons that we see when we first get in the car and step on the brake, all while showing the side-view image of the car), and it happens usually in the first 1-4 minutes of trip-time after getting in the car (happens while in Park, in Drive but stopped, while driving, basically in any condition you can imagine. This reboot would typically only happen once in the beginning of the drive, but I think I have seen it maybe more than once in a drive. But I'd say 90% of the time just once in the beginning of the drive.
Car information: December 2016, P100D Model S, just under 35K miles (still under warranty), originally Autopilot 2.0, but in late July was upgraded to FSD AP computer with purchase of FSD, AND had the MCU2 (with the associated new IC) installed. (oh, and with my new MCU installation, when the car was returned to me after service it had a prominent yellow border around the screen. My original MCU touch screen never had a yellow border to begin with! But that's just adding to my frustrating service story... I had it replaced and new touch screen is fine, but pretty unbelievable none the less).
(READ ON FOR MORE DETAILS IF YOU'RE INTERESTED BUT THE ABOVE INFO SHOULD SUFFICE FOR ANYONE THAT WANTS TO REPY)
More information:
Service Center- Centinela (Los Angeles)
So the variables go up from here... Around the time I had the new MCU installed, I began using the Teslacam feature with a USB stick, and shortly after that purchased a SAMSUNG T5 Portable SSD 500GB - Up to 540MB/s - USB 3.1 External Solid State Drive, Black (MU-PA500B/AM) from Amazon and began using that for my Teslacam. This comes into play later...
History of issues (perhaps some of these other issues are related?):
I had multiple issue after my MCU replacement in July. I not only had the IC reboot happening often (I didn't keep track at first, I had more pressing issues), I was having bigger problems with the AP visualization. On nearly every drive I had my repeater cameras (the two on the side that look rearward and are part of the backup camera visualization and Teslacam recording) blank out, just go black, and usually caused a message that said autopilot features unavailable and the IC visualization of cars, signs, road markings, etc would just disappear, usually not returning until after the car was parked for a period of time. Ugh. I also began having issues with the backup camera not saving to the Teslacam, even tho the backup camera continued to work fine, but not a huge deal.
I had to go back into Tesla about replacing the touch screen (oh and they forgot to reattach a wiring plug so my hazards didn't work for awhile after I first got my car back from the MCU2 install), and then back again for the autopilot/ visualization issues, rear camera not saving from Teslacam, and IC reboot. They claimed all 3 were fixed, and true enough the AP/visualization and the rear camera saving to drive issues were resolved but the IC reboots continued. I give credit to the service advisor that made an appointment to come back in without me even requesting it when I told him the IC was still rebooting, but I was just happy the other two issues were resolved, the IC I guess I can live with as it doesn't really interfere with driving or even AP use (tho just today I discovered that when on a phone call using BT through the car, the call is hung up, so now I am annoyed with this to the point where I'm writing this on the forums!).
I came into service now for the 4th time since the MCU2 installation upgrade, the issue was traced by the service technicians/engineers to a corrupted SSD, my Samsung I mentioned above. I had already tried re-formatting the drive many times myself as a troubleshooting idea, but they claimed that was the source of the reboots and when disconnected the IC reboots didn't occur. I took their word for it, received the car back, and stopped using the Teslacam all together. Well, sure enough, the problem happened again days later, and I even recorded it happening without the drive connected. Oh, and to add salt to the wound, the hazards weren't working again after getting my car back from service.
At this point I was pleased to hear that the Service Center agreed with me that the best course of action was to try replacing the entire IC. They sent Mobile Service to me but it turned out they had the wrong IC... Awesome. At least they reconnected the wiring for the hazards. Well, now they wanted the car back at the SC so they could do it properly, so I brought the car in that day. Apparently after they replaced the IC, the rebooting continued so they decided to order a whole new MCU2 (and IC) upgrade package.
After getting the car back a week later with the new IC and MCU2, I was told that maybe just to be safe I should try not using the Samsung SSD for awhile just as a baseline, they still believed it was the culprit or related to the reboots. I agreed and drove off using a simple USB Thumb drive (I really like using the Teslacam as a precaution just in case I need the footage if something happens to my car while driving!). The next day I had a reboot again at the beginning of the drive. Back to the drawing board. I haven't contacted Tesla and not sure I will as they just don't seem to have a handle on this issue and I'm apparently the first case, lucky me. Oh, and the right USB port was no longer powered after they returned the car to me, I had to go back for the 6th time since the original MCU2 upgrade to have them fix it... Now it's fixed.
I began using the SSD again because why not, the reboots are still happening no matter what I do. I even reformatted it again just in case, and I'm consistently getting reboots in the first 1-4 minutes of driving. I began experimenting with beginning my drive with it unplugged and then plugging in after a few minutes into my drive, and perhaps it's my imagination but seems like the reboots aren't happening as much, so perhaps there is something to the SSD affecting the reboots of the IC. I need to collect more data on this but I still suspect it's something else, just from the fact that the reboots have happened with the SSD completely unplugged from beginning to end of some of my driving trips.
For anyone that's read this far, wow, greatly appreciated... I know it's a lot of info and details but this is a weird issue that I'd like to resolve, so thank you for reading and any suggestions or info you have to share!
