green Profile picture
Mar 30, 2023 10 tweets 3 min read Read on X
So I decided to look into how Tesla does alternate routes (I know, late) fully expecting to see they just get a few alternatives from Google and that's it and... nope, there's nothing like it!
Instead they grab a route from google (if online nvigation enabled), and then feed that into tesla maps service (in the cloud). And that maps service returns possible alternatives (deduced by unknwon means). But that's not all!
A lot more interesting is that in addition to that they also query that service for "what are the parking lot outline at my location" and "hey, for this route I have, what else do I need to know".
This last part is interesting, because it tells the car in great detail map corrections like "there's a stop sign here", "crosswalk there" with great accuracy.
Also other useful information like lane info, directions of travel and whatnot.
And speed (to show you yellow/red path)
When people say "my car took the same route as before and this time drove better" - the map updates like this help immensely and is probably why.
And overall it seem to be updating certain elements in near realtime. This also includes rough road patches and such.
The car also feeds things like detected speed limits and realtime speeds there in return every 2 minutes or so.
Certainly helps keep maps a lot more current than even regularly updatable maps in cars are. And only relevant sections at that.
Basically it's like a waze service, but for the autopilot. Here is the output I got for the route from 35.93486,-84.014374 to 35.810833,-83.993889 the other day: pastebin.com/Z3ivF3Cu
the edge ids are relative to Tesla in car maps so the car knows what property to update.
And if you pay close attention, a bunch of elements presented list Tesla as the source. ImageImage
Looks like pastebin hates long pastes.
so here's a link that actually works. Thanks, rentry!

rentry.co/sgodk
btw I guess important corollary (that we mostly knew about) is - Autopilot performs better when you have a route set because if you don't, it does not fetch this "information about route ahead".
Keep this in mind with your testing.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with green

green Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @greentheonly

Aug 20, 2025
another replacement battery thread (sorry you'd have to bear with me for some time still as I explore the depths of my misfortune).

So I got the car today and found that Tesla changed the bettery to the -H index pack - the one they use in the LR++ (2020H2 cars), but it's a reman pack
While they of course are totally fine to use remanufactured packs owners hope to not end up in a worse situation than they were before.

In my case this basically means that the degradation of this pack is much worse than the original one I had.

Mine degraded from 96.7 -> 92.6 kWh = ~4.75%
Now I cannot really know what this pack was at when new, but we can pessimistically assume it was exactly at rated advertsed range (typically they are a bit better)
that puts it at 100.5 kWh or better new (I typicaly saw them coming out at 102).
So 100.5 -> 91 is 9.5% degradation.
Read 7 tweets
Apr 7, 2025
Got a bit of free time over the weekend and noticed that HW4 size of NNs in v13 ballooned from 2.3G total in v12.x to 7.5G on just node B in v13 (and 2.3g on node A).
(for comparison hw3 is 1.2G node A and 3.1 node B now on v12.6)

So I decided to look some more into it.
Just the same as on the hw3, node B now contains all the "secret" E2E bits that have some extra encryption applied to "protect" it.

Node A has 189 NNs and node B only has 110 NNs and of those 61 are shared between A and B. (so there goes your redundancy)

Interesting to see that there are 135 NNs that are shared between HW3 and HW4 in current releases.
It's also interesting that all those "factory driverless stuff" have a dedicated E2E set of (9 sub)networks which makes me think they might not be entirely as environment-agnostic as some people want to believe. (there are other E2E bits for highway, city streets and destination (for when you approach the destination), all these actually exist in two forms, "normal" and "low speed" (except factory where everything is low speed anyway).
Read 5 tweets
Jun 17, 2023
Impressions after nearly 600 miles on 11.4.3 with Elon mode (could not get a non-Tesla car to try in time).
It went much better than the prior experiment obviously.
Many contributing factors. I was not as late so I did not mind as much (still ended up 5 minutes late solely
because of FSD foolishness).
So I was more tolerant towards the constant flow of cars passing me on the right and merging in front of me.
It also helped that I did not need to watch for the dreaded nag.
Overall I spent a bunch of time thinking about it and came up with this:
If the car did not need my attention - I'd just plan for late arrival as much as possible and don't care of many of the current very annoying deficiencies.
They are only this annoying because I actually have to watch the car and so I notice them, as they greatly diverge from my
Read 11 tweets
Jun 13, 2023
Paging all hw4 radar deniers, I guess.

What is the first thing you do when you get a HW4 car? You take it apart of course ImageImageImageImage
ImageImageImage
Like really-really take it apart.
Because FCC pictures are... low res ;)
And old too. ImageImageImageImage
Read 6 tweets
Mar 26, 2023
Now that HW4 is widely available I got some firmware samples and discovered that:
The shipping version is internally called 2-SOC and has two possible camera layouts. The current one or the expanded one with added surround view cams (front bumper and two more)
The cameras run at 2880x1876 and run at( up to?) 45fps.
The main and backup cameras differs from the rest of them (and main and backup are a bit different too). vendor TBD.

new GNSS is Teseo V based.

Radar is confirmed ethernet or 192.168.90.110 internal IP.
But a lot more interesting is the 3-SOC version that seems to be up and coming? The camera layouts for that remain same though some internal deserializing routing differs.
There was a rumor that with the GPU in place heat output increased and HW4 was curtailed, so may be this is
Read 5 tweets
Feb 15, 2023
I am sure you are all eager to know more about HW4, so I am going to show you the refreshed car computer from a Model X. Just don't tell anybody you saw it, because it's really a secret still.
This unit made appearance at the EPC about a month ago, but the picture was hidden.
Looks like Tesla started to build cars with it but does not deliver them yet, I imagine the plan is to announce on March 1st that all cars off the line are already having it.
To start with sorta bad news, The form-factor is totally different, so definitely no retrofits on this one.
top/left is new unit, bottom - current plaid unit)
Read 19 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(