2025.14.7 Update

[Qixer01]

I’m in the same situation. Why is there so much disparity in updating CT owners? Is it location, safety score or date of purchase??? I’m a there a rational approach by Tesla?

I am a new owner. Took delivery on 5-13-25. Had software 2025.14.3.1. Received new software 2025.14.7 on 5-20-25.

Sponsored

 

[JerseyMike]

I’m in the same situation. Why is there so much disparity in updating CT owners? Is it location, safety score or date of purchase??? I’m a there a rational approach by Tesla?

on 2025.14.3.1 myself too....my 2019 model x just got 14.3.7 last night it has lifetime FSD though so maybe that helps


if you connect to wifi overnight and set the software screen to "Advanced" maybe it helps

I also sometimes toggle that screen and click on advanced.....recently did in the X


at least this is so much better than Ford.....updates there would take 6 months to a year and had to do some scary forced updating at times or modifications to the system manually if you really wanted new features

 

[L3it3R]

Does it fix the dangerous slamming of brakes on highway in cruise control and FSD? Wow, so startling and annoying as F! Does it even when there's nothing around.

Literally zero experience with that in my CT over the last 23,000 miles. In early days of FSD in my model 3, sure - anytime a slight rise in the highway occurred, a truck entered my lane, etc. But not in the CT, certainly not on FSD 13.x

 

[Cincycyber]

Does it fix the dangerous slamming of brakes on highway in cruise control and FSD? Wow, so startling and annoying as F! Does it even when there's nothing around.

Mine hasn't done that since first FSD release in September / October.

 

[tbuck]

Does it fix the dangerous slamming of brakes on highway in cruise control and FSD? Wow, so startling and annoying as F! Does it even when there's nothing around.

Just came back from my second big road trip (over 2700 miles). What I keep seeing is rapid deceleration with heavy regen when it things the speed limit drops. When this occurs, I see a phantom speed limit on the display. For example, going down Hwy 287 East/South from Amarillo, TX back to Dallas, I will be going 70 MPH and then suddenly drop to 50 MPH with not a sign in sight. Same thing happened on I40 eastbound in Amarillo - dropped from 60 down to 50...where there used to be long-term construction that finished up earlier this year. Late last year going through Colorado, I dropped from 75 down to 45 with someone on my tail going past a small town through which the road USED to go.

The truck does not "read" the speed limit signs. it only reads the map data to know what the speed limit is - which "should" match where the speed limit signs are.

This is a classic case of bad data and FSD will never be good enough until they can fix the underlying data. Whenever this happens, I now disconnect FST and provide a report before turning it back on.

 

[EMoeller]

Is there a way to force the truck to get updates? I'm still on 14.3.1 and not getting any updates popping up.

Not that I am aware of, BUT you might try stopping by your Tesla Service Center (no need to go in just park there) as the mere presence of your vehicle sometimes triggers updates.

 

[TyPope]

Just came back from my second big road trip (over 2700 miles). What I keep seeing is rapid deceleration with heavy regen when it things the speed limit drops. When this occurs, I see a phantom speed limit on the display. For example, going down Hwy 287 East/South from Amarillo, TX back to Dallas, I will be going 70 MPH and then suddenly drop to 50 MPH with not a sign in sight. Same thing happened on I40 eastbound in Amarillo - dropped from 60 down to 50...where there used to be long-term construction that finished up earlier this year. Late last year going through Colorado, I dropped from 75 down to 45 with someone on my tail going past a small town through which the road USED to go.

The truck does not "read" the speed limit signs. it only reads the map data to know what the speed limit is - which "should" match where the speed limit signs are.

This is a classic case of bad data and FSD will never be good enough until they can fix the underlying data. Whenever this happens, I now disconnect FST and provide a report before turning it back on.

That's actually not a bad idea, reporting changes via the FSD reporting.
Question though - Tesla uses Google Map data. Does Waze show the speed limit correctly there? I ask about Waze because Google uses Waze to make road changes. I was an editor on Waze (not FOR the company, just on my own). I would submit a change and a reviewer would ask a question or two and then it'd be fixed in the map data.

I wonder if Tesla uses the live version of google maps and that reporting changes through Waze is the best way to make changes.

(reminds me... for some reason, Tesla skips a turn on one route south from my house. It makes the turn but the navigation never shows it. It's just all "12 miles to next turn"... Well, except for the one just 4 miles down the road... a secret turn, if you will.

 

[tbuck]

That's actually not a bad idea, reporting changes via the FSD reporting.
Question though - Tesla uses Google Map data. Does Waze show the speed limit correctly there? I ask about Waze because Google uses Waze to make road changes. I was an editor on Waze (not FOR the company, just on my own). I would submit a change and a reviewer would ask a question or two and then it'd be fixed in the map data.

I wonder if Tesla uses the live version of google maps and that reporting changes through Waze is the best way to make changes.

(reminds me... for some reason, Tesla skips a turn on one route south from my house. It makes the turn but the navigation never shows it. It's just all "12 miles to next turn"... Well, except for the one just 4 miles down the road... a secret turn, if you will.

Good question! I know you can also report discrepancies with Google Maps within the Google Maps app itself (on your phone). No idea about Waze, however.

 

[TyPope]

Good question! I know you can also report discrepancies with Google Maps within the Google Maps app itself (on your phone). No idea about Waze, however.

Back when I was actively doing it, they told me to do so through Waze. It's been 3 years. So yeah, however you need to make changes to the underlying map data, do it.

 

[LiveFreeOrDieBob]

The truck does not "read" the speed limit signs. it only reads the map data to know what the speed limit is - which "should" match where the speed limit signs are.

Not sure that’s true. I thought I remembered someone on the Tesla AI team saying that they didn’t TEACH it to read signs, but it figured that out to some degree on its own. AI will do that sometimes - it can learn things you don’t expect because it has so many inputs/signals to imbed into the model that it can learn things you never expected, or associate situations and data with reactions that weren’t predicted.

 

[cybrtrkKC]

When are our B pillar cameras going to work for sentry sigh

 

[SCTesla]

The truck does not "read" the speed limit signs. it only reads the map data to know what the speed limit is - which "should" match where the speed limit signs are.

This is completely false.

The truck does read SL signs and references map data. This has been proven numerous times. That's why temporary speed limit signs, even put up within the last 30 min, my truck will read (and testers like Dirty who has put up his own signs).

The biggest issue with V13 is that all cars read minimum speed limit signs, signs on frontage roads, and even signs on the back of semis as the speed limit. What it sees takes precedence over the map data.

 

[tbuck]

This is completely false.

The truck does read SL signs and references map data. This has been proven numerous times. That's why temporary speed limit signs, even put up within the last 30 min, my truck will read (and testers like Dirty who has put up his own signs).

The biggest issue with V13 is that all cars read minimum speed limit signs, signs on frontage roads, and even signs on the back of semis as the speed limit. What it sees takes precedence over the map data.

I will have to challenge you on this one. Here are some specific examples I come across regularly - event under the last 14.6 update (have not received 14.7 yet). This has also been consistent since FSD was first released for the CT. While it may have the ability to interpret some signs, it does not read signs regularly and changes speed when there are no signs (not even speed limit signs - so one cannot say it misinterpreted another sign as a speed limit sign).

- Vehicle "sees" speed limits when there are no signs and adjusts speed accordingly - but matches what Google thinks they are.
- Hit changes in speed limits (increased) for which the truck does not "see".
- Going through a construction zone. They are building a Wells Fargo two-building + separate garage just down the street from me now and have been for over a year. I drive through it nearly daily, multiple times. However, while the CT negotiates it well, it never adjusts to the temporary speed limit signs and so I dial it back using the scroll wheel. They pulled up the temp signs a few weeks ago and so I no longer have to dial it back.
- Last Friday, I was driving south on Colorado 550 between Ouray and Durango. This is a twisting two-lane, narrow mountain road with a steep (and deep) drop-off on one side. FSD did pretty well, but never adjusted to the speed limit signs for sharp turns. I was usually able to dial it back, but had to take over on two occasions. Same thing with a construction area where it was down to one lane (shared for both directions). It handles the temporary stop light well, but not the temporary speed limit signs.
- For some long-duration construction projects, the speeds are updated in the data and the truck does slow down properly. However, they do not always change those speeds back after construction (such as my experience this past Sunday eastbound through Amarillo when the vehicle decided the construction speed limit was still there, although all the signage said 60 MPH). It has the right speed limit from when I went through in December of last year - but that is no longer there (and why I know that it was there for many months previously).

I have seen Dirty Tesla's videos in which he comments on the vehicle seeing or not seeing specific changes.

The other issue is that the car does not learn on its own. It only runs the trained model sent to it and interprets the world around it based upon the trained parameters in the model. It may interpret something in a way the engineers did not expect or did not realize was in the training data used to generate the current model, but that does not necessarily mean the vehicle is learning on its own.

Another example of this is when the vehicle is not centering in the lane. You can apply a little pressure on the steering wheel and have it center in the lane. It will even keep that for a while. However, it will return to its "normal" training and begin hugging the left side of the lane again within 10 - 15 minutes (in most cases) as that is its interpretation of the real world against its training model entails.

I would love for the truck to do a better job of interpreting speed limit signs and temporary signs more than it currently does. If it really did read speed limit signs, most of these issues would not exist - slowing down when there is no sign - not speeding up when there is a sign - or (another situation I have hit on this last trip twice) slowing down, speeding up, and then slowing down again within less than a quarter mile and the screen showing different speed limits when there were no signs anywhere nearby of any type.

 

[SCTesla]

I will have to challenge you on this one. Here are some specific examples I come across regularly - event under the last 14.6 update (have not received 14.7 yet). This has also been consistent since FSD was first released for the CT. While it may have the ability to interpret some signs, it does not read signs regularly and changes speed when there are no signs (not even speed limit signs - so one cannot say it misinterpreted another sign as a speed limit sign).

- Vehicle "sees" speed limits when there are no signs and adjusts speed accordingly - but matches what Google thinks they are.
- Hit changes in speed limits (increased) for which the truck does not "see".
- Going through a construction zone. They are building a Wells Fargo two-building + separate garage just down the street from me now and have been for over a year. I drive through it nearly daily, multiple times. However, while the CT negotiates it well, it never adjusts to the temporary speed limit signs and so I dial it back using the scroll wheel. They pulled up the temp signs a few weeks ago and so I no longer have to dial it back.
- Last Friday, I was driving south on Colorado 550 between Ouray and Durango. This is a twisting two-lane, narrow mountain road with a steep (and deep) drop-off on one side. FSD did pretty well, but never adjusted to the speed limit signs for sharp turns. I was usually able to dial it back, but had to take over on two occasions. Same thing with a construction area where it was down to one lane (shared for both directions). It handles the temporary stop light well, but not the temporary speed limit signs.
- For some long-duration construction projects, the speeds are updated in the data and the truck does slow down properly. However, they do not always change those speeds back after construction (such as my experience this past Sunday eastbound through Amarillo when the vehicle decided the construction speed limit was still there, although all the signage said 60 MPH). It has the right speed limit from when I went through in December of last year - but that is no longer there (and why I know that it was there for many months previously).

I have seen Dirty Tesla's videos in which he comments on the vehicle seeing or not seeing specific changes.

The other issue is that the car does not learn on its own. It only runs the trained model sent to it and interprets the world around it based upon the trained parameters in the model. It may interpret something in a way the engineers did not expect or did not realize was in the training data used to generate the current model, but that does not necessarily mean the vehicle is learning on its own.

Another example of this is when the vehicle is not centering in the lane. You can apply a little pressure on the steering wheel and have it center in the lane. It will even keep that for a while. However, it will return to its "normal" training and begin hugging the left side of the lane again within 10 - 15 minutes (in most cases) as that is its interpretation of the real world against its training model entails.

I would love for the truck to do a better job of interpreting speed limit signs and temporary signs more than it currently does. If it really did read speed limit signs, most of these issues would not exist - slowing down when there is no sign - not speeding up when there is a sign - or (another situation I have hit on this last trip twice) slowing down, speeding up, and then slowing down again within less than a quarter mile and the screen showing different speed limits when there were no signs anywhere nearby of any type.

Tesla says the vehicles recognize signs.
Greentheonly says it.
Testers have proven it.
Many here anecdotally have also seen it.

There's no debate. The map data is now updated by each car. So those bad reads of minimum speeds, temp signs, even signs on trucks get published if enough of the fleet reports it (Green showed this).

The sign has to be a specific size, which was proven by multiple people.

Your instances of bad speeds have reason (i.e. temporary, construction, highway signs, etc.) , but they do not prove your theory that everyone is in on a big lie.

All Tesla vehicles recognize and use vision to publish speed limit signs as of August 31, 2020.

V12 was much better with this. V13 picks up a lot of incorrect signs and publishes them as speed limits. US Route 15 in South Carolina and Minimum 45 in Georgia suck.

edit: There's a video of using black electrical tape to change the speed will trick FSD as well. That's another point of proof.

 

[tbuck]

Tesla says the vehicles recognize signs.
Greentheonly says it.
Testers have proven it.
Many here anecdotally have also seen it.

There's no debate. The map data is now updated by each car. So those bad reads of minimum speeds, temp signs, even signs on trucks get published if enough of the fleet reports it (Green showed this).

The sign has to be a specific size, which was proven by multiple people.

Your instances of bad speeds have reason (i.e. temporary, construction, highway signs, etc.) , but they do not prove your theory that everyone is in on a big lie.

All Tesla vehicles recognize and use vision to publish speed limit signs as of August 31, 2020.

V12 was much better with this. V13 picks up a lot of incorrect signs and publishes them as speed limits. US Route 15 in South Carolina and Minimum 45 in Georgia suck.

edit: There's a video of using black electrical tape to change the speed will trick FSD as well. That's another point of proof.

Not arguing here - but this does not match the reality that most of us are seeing. Yes, Tesla has said it (as of update 2024.26.1), but it is still reading map data most of the time. That, or it is trying to blend the two.

The black tape deal was back in 2020 when researchers were testing things - that is when Tesla started relying on map data until they could figure things out.

Again, still a work in progress, but still not relying on reading speed limit signs most of the time.

Sponsored