Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register
This site may earn commission on affiliate links.
Do we even know where Tesla gets its map data from? I've seen a hodgepodge of theories including Google, Open Street Maps and TomTom in the past but nothing definite.

There's one highway I drive that is 55 MPH but FSD always has the speed limit at 45 when I first turn on until it sees the speed limit sign ¼ mile later. I assume that's map data but no idea where it would come from.
The map may not be the problem. The handshaking between the city stack and the highway stack could be out of sync.
In my area, sometimes FSD shows speed limit 20mph but the actual speed limit is 65mph on a long freeway ramp. Sometimes FSD takes the wrong freeway entrance where there are 2 entrances close to each other and on the same direction.
 
From what I can tell with teslafi, their mapupdates aren't showing correctly.....at least for me.....the newest map update i see is 5/16
Something has changed completely with the way maps are made available and how Teslafi shows their install.

In the past I'd get a notification, go off to connect to wifi somewhere, it would download and install and Teslafi would indicate what happened.

For the longest time I had the really old 2023 maps. When we got V12.3.3 I knew from the forums there was a mapping update to 2023.44 and over a week my phone app showed I had a download to do but neither the car nor Teslafi showed anything pending.

I drove over to the Service Centre and hopped on their wifi, the notification went away on my phone but nothing happened for over 30 minutes so I gave up and by the time I was home, it was telling me to sign onto wifi to download an update.

I put in a service request and they told me I had the latest version and I pointed out the problem with app telling me to connect to download an update and they did something that cleared the notification in my app.

When we downloaded V12.3.6, the same thing happened again. We downloaded the last day at our stay at this place with wifi in the driveway and installed before the drive home. By the time I was home, my phone app was telling me to update.

When I came back here weeks later, it must have hopped onto the wifi because the app notification went away and I finally had the 2023.44 maps.

We're back here again so downloaded 2024.14.9 while unloading the car. When the car is parked after unloading, it doesn't have wifi so today we moved it back into range but only the games downloaded.

My dh is arguing with me that the car says we have the latest version of updates and Teslafi doesn't show any pending downloads but I suspect as soon as we leave here, and the car doesn't have wifi, I'll go back to having that notification of a pending download if the maps haven't updated by then.

In the past, I knew I was awaiting a NAV update because both the car and Teslafi told me (important info since they are large and take a long time to download) and when I was sitting in the car after triggering their download, I got the same UI as with a firmware update, with notice I had connected, what was downloading, and how far along in the process I was.

Now, aside from me getting app notification, I wouldn't know the maps were out of date if I wasn't a member of this forum. The last map update Teslafi shows me receiving was October of last year when NA 2023.20 NAV was made available to me after I installed 2023.27.6. There is no indication at all that I have NA.2023.44 (but the car tells me I do.)

Tesla is making it much harder for those of us without wifi at our parking spot to keep our cars updated. If I randomly have to connect my car to wifi for hours/days on end until tesla decides to send the new maps, that's not workable for me.

The mapping currently is total crap in my area; it coded the highway number as the speed limit so the car can't be used on either AP or FSD without major interventions as it is constantly dropping the speed to 60kph each time we drive by a highway marker, then accelerating back up to 80 kph each time it passes an actual speed limit sign. And it won't let us use autosteer at more than 10 kph over the limit so when it thinks it is 60, we have to turn off autosteer. These are mapping errors (not the car reading signs) because when we turn off highway 17 onto highway 20, the car brakes to 20kph (from almost 80) and there are no highway number signs there, just the street name because it is on the other side of the highway 17 that highway 20 begins. The mapping coding is wrong and therefore we know to disengage FSD as it starts into the turn to avoid the braking (and risk being rear-ended for apparently stopping with no reason in the street.)
 
  • Informative
Reactions: VanFriscia
There's one highway I drive that is 55 MPH but FSD always has the speed limit at 45 when I first turn on until it sees the speed limit sign ¼ mile later. I assume that's map data but no idea where it would come from.
Any chance that is highway 45? The majority of my incorrect speed limits are traced back to the highway numbers. The other place it does it for me is where there was construction with a lower speed limit for a while. Oh, and every single 'lower speed limit ahead' sign. It changes speed at the sign with the arrow, not at the speed limit begins sign.

And, of course, it reads all speed limit ends signs as whatever speed limit is ending. And ignores all orange signs (school zones, lower limit for curves and on-ramps.)

Suffice to say, FSDs remains FSDjunk as far as I'm concerned, and the junk mapping they use is 90% of the issue on my weekly 3 hour drive.
 
Any chance that is highway 45? The majority of my incorrect speed limits are traced back to the highway numbers. The other place it does it for me is where there was construction with a lower speed limit for a while. Oh, and every single 'lower speed limit ahead' sign. It changes speed at the sign with the arrow, not at the speed limit begins sign.

And, of course, it reads all speed limit ends signs as whatever speed limit is ending. And ignores all orange signs (school zones, lower limit for curves and on-ramps.)

Suffice to say, FSDs remains FSDjunk as far as I'm concerned, and the junk mapping they use is 90% of the issue on my weekly 3 hour drive.
it's actually highway 55! It's a state highway with stoplights so it's not the V11 stack, either. It happens when I first turn on (from a stoplight intersection.) As soon as it sees a speed limit sign it fixes itself and it's fine. MN state highway signs are blue so they aren't easily confused for speed limit signs like some others can be.
 
Something has changed completely with the way maps are made available and how Teslafi shows their install.

In the past I'd get a notification, go off to connect to wifi somewhere, it would download and install and Teslafi would indicate what happened.

Interesting. I have never gotten a notice that new maps were ready to be downloaded. Maps have always just dropped on their own. I got the 2024 maps early last week and didn't realize it until a 7 year problem with navigation routing was fixed much to my surprise.
 
Have you successfully flipped your car upside down on the visualization screen when the car is parked? I tried but I couldn't.
I have faith in the Autopilot team programmers!
If you were actually to flip your car upside down, I'm very confident it would render perfectly on the visualization screen.

Should anyone doubt this, I invite him to prove me wrong...
 
I actually had an FSD failure yesterday, something that is becoming pretty rare for me. It seems that FSD still can’t handle stoplights that are flashing red. I don’t know if this is due to lack of training or something else, but clearly it can handle flashing yellow lights, so I’m not sure why it shouldn’t be able to handle flashing red.
 
The map may not be the problem. The handshaking between the city stack and the highway stack could be out of sync.
In my area, sometimes FSD shows speed limit 20mph but the actual speed limit is 65mph on a long freeway ramp. Sometimes FSD takes the wrong freeway entrance where there are 2 entrances close to each other and on the same direction.
Wrong freeway exit, my example:
There is a freeway exit in NC, I40 connecting to I540 that software has never properly made.

Instead of heading to the “south” exit, it always decides to go to the “north”.

Then, when I disconnect and reconnect it proceeds to know that it should exit “south” but instead of exiting it decides to stay on the I 40 shoulder lane and go straight.

That plus the program’s tendency to always move into lanes that are slated to shortly turn right or end makes using it without disengagements in the Triangle impossible.
 
  • Like
Reactions: zoomer0056
Tesla failed once again as a “tech company”.

The Wall Connector manual advertised that it supports WPA2/WPA3 security but it indeed does not. It only supports WPA2. This might not be an issue for those running older WAPs or older home routers, but it will be once you upgrade to devices with WiFi 6E standard as the standard does NOT support outdated WPA2 security and requires WPA2/WPA3 mixed or WPA3 mode.
 
@AlanSubie4Life have you seen the recent Progressive Insurance Commercial about the bank robbery?

They promote being at a complete stop at a stop sign for multiple seconds, and they stopped significantly before the line. 🤣

1718812124659.png
 
Hoping someone knows about the new strike removal system and when it's supposed to take effect. I have the new Highland on v12 (2024.14.9) FSD 12.3.6.
Are FSD strikes supposed to fall off after 1 week of no strikes? I have had a full week and I still have 4 strikes.
Also, if I get my 5th strike the last day before FSD expires, and I wait a week to re-subscribe, will the FSD time-out resume, or will the week I am unsubscribed count toward the 1 week time-out period?
 
Hoping someone knows about the new strike removal system and when it's supposed to take effect. I have the new Highland on v12 (2024.14.9) FSD 12.3.6.
Are FSD strikes supposed to fall off after 1 week of no strikes? I have had a full week and I still have 4 strikes.
Also, if I get my 5th strike the last day before FSD expires, and I wait a week to re-subscribe, will the FSD time-out resume, or will the week I am unsubscribed count toward the 1 week time-out period?
Read here. But don't worry too much about strikes. You will know how to avoid strikes after getting familiar with FSD in a short time.

 
Interesting. I have never gotten a notice that new maps were ready to be downloaded. Maps have always just dropped on their own. I got the 2024 maps early last week and didn't realize it until a 7 year problem with navigation routing was fixed much to my surprise.
That's what I would expect if you have wifi at your parking spot. There's no need to tell the owner to go find wifi in order to update maps, it just happens. The only reason you are aware of other updates is that they require an install but games updates and maps don't so you don't see them happening. (I do, and for games in particular, it is a pain because I drive 25 minutes to get to wifi for a new update, download and install (usually an hour), the update available message clears from my phone and car, and then 5 minutes into the drive home, I get another update available message.)

I don't have regular access to wifi, so tesla used to notify me explicitly that there was a mapping update to download, telling me through an 'update available' icon in the car. And, once the car was on wifi, a 'regular' update experience (immediately the update would download, complete with a progress bar, the only difference is no install after download was required.)

Something appears to have changed in the programming and it no longer appears in the car, but my app shows update available and tells me to connect to wifi. But when I do, nothing happens, unlike before. And if my car is connected for days, at some point the download happens and then my app returns to normal but I get no notifications at all that anything has changed, either in my app or Teslafi. But the car then shows I have different version of maps.
 
@AlanSubie4Life have you seen the recent Progressive Insurance Commercial about the bank robbery?

They promote being at a complete stop at a stop sign for multiple seconds, and they stopped significantly before the line. 🤣

View attachment 1057834
To be fair, that's a crosswalk line, not a stop line. You are required to stop 3 feet before the crosswalk if there is no stop line painted, at least in Michigan (to the best of my recollection of the relevant traffic code sections.)
 
Read here. But don't worry too much about strikes. You will know how to avoid strikes after getting familiar with FSD in a short time.

Thanks for the reply! I see, so since I have 12.3.6, I need to have 12.4 in order for that system to be enacted? I have only had a Tesla for less than a month, so I'm still learning about the software and updates. I had a VW ID4 before this, and in the 3 years I owned it, we got only one OTA update about a month before I returned it, and the update was only to prepare the software for future OTA updates! 😂
 
Hoping someone knows about the new strike removal system and when it's supposed to take effect. I have the new Highland on v12 (2024.14.9) FSD 12.3.6.
Are FSD strikes supposed to fall off after 1 week of no strikes?
Not on the version you have. The strike roll-off feature comes as part of FSD 12.4.1 that is in 2024.15.5.

Also, if I get my 5th strike the last day before FSD expires, and I wait a week to re-subscribe, will the FSD time-out resume, or will the week I am unsubscribed count toward the 1 week time-out period?
When you get striked-out it lists the date/time that suspension expires. I assume it doesn't matter if your FSD subscription is active or not. (Since it suspends basic Autopilot as well.)