andrewsjra
Member
I’m having mine checked with Tesla now along with some other things. I’ll post what they determine.
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Keeping Sentry Mode on all the time seems to help - maybe the car isn't handling "deep sleep" properly wrt the USB ports?
Mobile service came out and ended up changing the USB Hub (Part number FRONT(1522264-00-B). Next day warning popped up again and turned camera icon off. Had to unplug drive and plug back in. warnings have decreased to once a week but camera icon disappears several times a week and stays gone until either drive is unplugged and then plugged back in or it seems to come back on its own after sitting all night.Update for me. Warning popped up with only the OEM charge pad plugged into USB C plug. Unplugged pad and warning stayed on screen until reset.
made appointment at service center and then they changed appointment over to mobile service. Will report back but have a feeling they will get the drive back online and then call it good. Although I was very specific about what is happening I feel like they are just randomly saying stuff to make me go away.
About ~6mo. ago this would happen every single time I got into the car and often a few time during a drive. After maybe 2 mo. of that, it began to only happen every few weeks.I've had this issue extremely sporadically. For some reason it has just gone away for the last two months. When it was happening I wasn't getting much luck from the service team as it was so damn sporadic
It's working again using a USB stick. Format as ExFat; containing "TeslaCam" folder.Using SD/microSD card reader. Receiving the dreaded errors below. Option for MCU to Format USB unavailable.
- UI_a134 USB drive has no filesystem. Drive will not mount and should be unplugged.
- UI_a112 USB device malfunction - Center console port. Unplug device from USB port.
Tried to substitute with a flash drive, and there's no TeslaCam (icon isn't available). Which is odd because in Safety & Security > Format USB is available. The flash drive is named "TESLADRIVE" and formatted as ExFAT. (However, it's missing the folder "TeslaCam". Will try to create folder and hope it works.)
2021.32.22 installed 25-September-2021
Some people in the other thread say a reboot clears the USB error. I think everyone the experiences errors after an update should reboot first before trying other things.It's working again using a USB stick. Format as ExFat; containing "TeslaCam" folder.
Wonder if the latest version (inadvertently) blocks hubs and card readers...?
How are you able to see the UI_a134 and UI_a112 portions of the error messages?Using SD/microSD card reader. Receiving the dreaded errors below. Option for MCU to Format USB unavailable.
- UI_a134 USB drive has no filesystem. Drive will not mount and should be unplugged.
- UI_a112 USB device malfunction - Center console port. Unplug device from USB port.
Tried to substitute with a flash drive, and there's no TeslaCam (icon isn't available). Which is odd because in Safety & Security > Format USB is available. The flash drive is named "TESLADRIVE" and formatted as ExFAT. (However, it's missing the folder "TeslaCam". Will try to create folder and hope it works.)
2021.32.22 installed 25-September-2021
I’ve gotten this same “Alert” also after updating to 2021.32.22. I’ve tried reformatting and rebooting and still getting the same error. It seems to still function but still has the alert. I’ve seen others mentioning about it as a firmware issue so hopefully Tesla addresses this with the next update. Just sharing that you are not alone.How are you able to see the UI_a134 and UI_a112 portions of the error messages?
It's working again using a USB stick. Format as ExFat; containing "TeslaCam" folder.
Wonder if the latest version (inadvertently) blocks hubs and card readers...?
Some people in the other thread say a reboot clears the USB error. I think everyone the experiences errors after an update should reboot first before trying other things.