USB not working

[Hotrode1970]

I have followed all the steps, correct format, etc and yesterday the light show worked, today it would not. Tesla 2024 Y would not recognize the USB. I tried the USB in computer and it worked. Not sure what is happening.

TIA

[Maxgagne4]

Same problem, worked 1 time only...

[deepcoder]

I'm still scratching my head to get a 100% solution, this is my best to date. Still has some oddities. However, I am able to get the Tesla to correctly 'see' the 5 key functions (LightShow, Boombox, Lock Chime, Music and Tesla Camera) with only one noted issue on a 1 TB USB nvme drive along with operation of a USB game wireless controller usb dongle (note my USB wireless game controller dongle requires a USB 3 to USB 2 A to A extension cable to be seen by Tesla).

To date, most every new update to the vehicles software seems to change some of these configurations. Almost like there are different branches of the USB support code that gets merged in to each release of the Tesla software package.

Current car configuration :
US Tesla Model 3 'highland' Rear wheel drive
software : v12 (2024.33.35)

Good hunting!

# new partition of 1 TB nvme drive on Tesla with new 4 port usb-a 3.2 hub
# 18-Nov-2024
# MacOS 15.1 Sequoia
# Aceele 10Gbps USB 3.2 Hub with 4 USB A 3.2 Ports
# Amazon : https://www.amazon.com/dp/B0C3GRN29P?th=1
# DOCKCASE Pocket M.2 2230 NVMe SSD Enclosure
# Amazon : https://www.amazon.com/gp/product/B0CB3K5ZVF?th=1

# Issues:
# only first 7 or so of the horn sounds on usb are visible

sudo diskutil list

# NOTE : replace /dev/disk2X with proper disk number referenece, aka replace X with 0... 9
sudo diskutil partitionDisk -noEFI /dev/disk2X 3 GPT ExFAT TESLADRIVE 600G ExFat LIGHTSHOW 1G ExFAT MEDIA R

#Finished partitioning on disk24
#/dev/disk24 (external, physical):
#   #:                       TYPE NAME                    SIZE       IDENTIFIER
#   0:      GUID_partition_scheme                        *1.0 TB     disk24
#   1:       Microsoft Basic Data TESLADRIVE              600.0 GB   disk24s1
#   2:       Microsoft Basic Data LIGHTSHOW               1.0 GB     disk24s2
#   3:       Microsoft Basic Data MEDIA                   423.2 GB   disk24s3

mkdir /Volumes/TESLADRIVE/TeslaCam
mkdir /Volumes/TESLADRIVE/TeslaCam/RecentClips
mkdir /Volumes/TESLADRIVE/TeslaCam/SavedClips
mkdir /Volumes/TESLADRIVE/TeslaCam/SentryClips

# NOTE : replace {Lock chime source directory} with correct directory
cp '{Lock chime source directory}/LockChime.wav' /Volumes/TESLADRIVE/

# NOTE : replace {Light show source directory} with correct directory, include ending "slash" /
mkdir /Volumes/LIGHTSHOW/LightShow
cp '{Light show source directory}'* /Volumes/LIGHTSHOW/LightShow/

# NOTE : replace {Boombox source directory} with correct directory, include ending "slash" /
mkdir /Volumes/MEDIA/Boombox
cp '{Boombox source directory}'* /Volumes/MEDIA/Boombox/

# NOTE : replace {Music source directory} with correct directory, include ending "slash" /
mkdir /Volumes/MEDIA/Music
cp -R {Music source directory}/* /Volumes/MEDIA/Music/

# this 'touch' might be required to get the car to reread the files. It appears that the car may cache file info somewhere.
cd /Volumes/MEDIA
find . -type f -exec touch {} +
 cd /Volumes/LIGHTSHOW
find . -type f -exec touch {} +
cd /Volumes/TESLADRIVE
find . -type f -exec touch {} +

[iuliuvisovan]

I'm still scratching my head to get a 100% solution, this is my best to date. Still has some oddities. However, I am able to get the Tesla to correctly 'see' the 5 key functions (LightShow, Boombox, Lock Chime, Music and Tesla Camera) with only one noted issue on a 1 TB USB nvme drive along with operation of a USB game wireless controller usb dongle (note my USB wireless game controller dongle requires a USB 3 to USB 2 A to A extension cable to be seen by Tesla).

To date, most every new update to the vehicles software seems to change some of these configurations. Almost like there are different branches of the USB support code that gets merged in to each release of the Tesla software package.

Current car configuration : US Tesla Model 3 'highland' Rear wheel drive software : v12 (2024.33.35)

Good hunting!

# new partition of 1 TB nvme drive on Tesla with new 4 port usb-a 3.2 hub
# 18-Nov-2024
# MacOS 15.1 Sequoia
# Aceele 10Gbps USB 3.2 Hub with 4 USB A 3.2 Ports
# Amazon : https://www.amazon.com/dp/B0C3GRN29P?th=1
# DOCKCASE Pocket M.2 2230 NVMe SSD Enclosure
# Amazon : https://www.amazon.com/gp/product/B0CB3K5ZVF?th=1

# Issues:
# only first 7 or so of the horn sounds on usb are visible

sudo diskutil list

# NOTE : replace /dev/disk2X with proper disk number referenece, aka replace X with 0... 9
sudo diskutil partitionDisk -noEFI /dev/disk2X 3 GPT ExFAT TESLADRIVE 600G ExFat LIGHTSHOW 1G ExFAT MEDIA R

#Finished partitioning on disk24
#/dev/disk24 (external, physical):
#   #:                       TYPE NAME                    SIZE       IDENTIFIER
#   0:      GUID_partition_scheme                        *1.0 TB     disk24
#   1:       Microsoft Basic Data TESLADRIVE              600.0 GB   disk24s1
#   2:       Microsoft Basic Data LIGHTSHOW               1.0 GB     disk24s2
#   3:       Microsoft Basic Data MEDIA                   423.2 GB   disk24s3

mkdir /Volumes/TESLADRIVE/TeslaCam
mkdir /Volumes/TESLADRIVE/TeslaCam/RecentClips
mkdir /Volumes/TESLADRIVE/TeslaCam/SavedClips
mkdir /Volumes/TESLADRIVE/TeslaCam/SentryClips

# NOTE : replace {Lock chime source directory} with correct directory
cp '{Lock chime source directory}/LockChime.wav' /Volumes/TESLADRIVE/

# NOTE : replace {Light show source directory} with correct directory, include ending "slash" /
mkdir /Volumes/LIGHTSHOW/LightShow
cp '{Light show source directory}'* /Volumes/LIGHTSHOW/LightShow/

# NOTE : replace {Boombox source directory} with correct directory, include ending "slash" /
mkdir /Volumes/MEDIA/Boombox
cp '{Boombox source directory}'* /Volumes/MEDIA/Boombox/

# NOTE : replace {Music source directory} with correct directory, include ending "slash" /
mkdir /Volumes/MEDIA/Music
cp -R {Music source directory}/* /Volumes/MEDIA/Music/

# this 'touch' might be required to get the car to reread the files. It appears that the car may cache file info somewhere.
cd /Volumes/MEDIA
find . -type f -exec touch {} +
 cd /Volumes/LIGHTSHOW
find . -type f -exec touch {} +
cd /Volumes/TESLADRIVE
find . -type f -exec touch {} +

This works! Thanks alot!! I've struggled with this for weeks - all the tutorials either don't cover all the cases, are for older models or are using Windows. Cheers for this!