green Profile picture
Feb 15, 2019 37 tweets 9 min read
Recently the Tesla "shadow mode" has been in the news prominently again with raging debates if it exists or not and if it does - to what extent.

Let me explain to you what I learned on this topic in my reasearch #TSLA #TSLAQ 1/
We'll start with the bitter truth. The "shadow driver that just sits there in the computer comparing notes and sending discrepancies and interesting events to Tesla" is a myth. I used to think people just misunderstood Elon, but now I believe Tesla lies about it on purpose 2/
What Tesla actually has is automatic data collection of "events". This data collection has two facets: fixed and "campaigns" as I am going to refer to them. The difference is the "fixed" events are hardcoded in the code while "campaigns" are uploaded to (some) cars often 3/
So what fixed campaigns are there? Obviously if you had an airbag deploy event or approach something real close at high speed - this kinds of events generate some camera footage and some metadata (more on it later) and sends it to Tesla. 4/
here's a crash footage sample: 5/
Here's a "sidesweep" sample: 6/
They also collect crashdumps if software crashed (happens very often), but this is boring so we will not explore it here.

Now the other fixture of fixed events is "autopilot trip logs" - these are ALWAYS collected. Yes, even if you opt out of data collection 7/
What's in there? Entire route you took from placing car into D to placing it into P. The route is split into "buckets" describing how fast you drove, was autopilot available or not, how well was the road recognized by AP and such. Like this:
8/
different colors you see in that picture represent availability of AP, since we needed to select only some stuff from what was being recorded, but there's much more in there of course.

Again, this data is sent to Tesla at all times and also over cell connection. 9/
I think this is how they publish those "X miles on autopilot" and such stats.
Another one of this kind is a "disengagement report". It sounds exciting, but is actually rather boring. The data there is coordinates, how did you disengage, speed, heading and time 10/
no pictures in those fixed disengagement reports so they are really small (under 1kb).

Now a more interesting topic is "campaigns" as I am going to call them, they are usually updated daily, but I have seen more and less frequent occurences We are on campaign 260 today: 11/
Tesla uploads what they call "triggers" to some cars by some criteria (mostly related to how often you drive it seems, also if you are on wifi often). These criteria outline what sort of conditions they are looking for and what data to collect. The results are only via wifi 12/
If the car does not get on wifi in some time the results expire and are deleted. The triggers themselves also have an expiration data (typically 1 week) and also a limit on number of snapshots they can generate (varies). 13/
Additionally when a trigger is hit car checks with mothership with some general information about it and mothership might instruct the car to discard the results without sending (criteria unknown) 14/
Triggers actually have a huge list of things they can match from general vehicle position/state to individual image "labels" (made by NNs) from any camera, to some internal autopilot state. 15/
Often they also have a blanket "starfish" trigger that would fire ~30 seconds after any other trigger and would collect internal autopilot object recognition status. If we were to draw this status on a blank canvas, it looks like this: 16/
it's actually a bit more detailed. This file is relatively small (~10MB) compared to what is conveyed but it only useful in conjunction with some actual pictures to see how good are the detections. data conveys about 2 minutes of activity. 17/
the "image NN labels" are actually not text labels, but raw NN output ~4K in size that allows them to fine-tune their detections to produce less false positives and in general fill their library of particular objects based on NN raw output. 18/
From what I can tell, almost all cars get these "campaigns", but not every car gets all of them. You see these uploads as big spikes on your car wifi stats if you track that stuff.

Now look at a sample campaign from last week to see what's in there: 19/
Every trigger has a name and I will use these and describe what they do:
img-parking-aisle: if path planning believes you are in a parking isle it takes latest frame from all cameras (~2M per camera)
20/
img-sustained-steer-gt8: if you move under 80mps and and moving faster than 8 mps and steering wheel is at 55.75 angle it captures last 6 sec video and latest still frames from fisheye, main and pillar cams - only two samples requested probability 1% 21/
img-sustained-steer-dc: same as above only you are in lat 37.381414..37.417791 lon -122.171607..-122.133067 rectangle

img-sustained-steering: like above but lat 32.734052..41.91059 lon -125.083973..-114.038702, speed between 4 and 12 mps steering above 80deg. 22/
img-mu-estimate: some IMU estimation, 1 sample, collects 9 frames from main camera at 1 fps when car is moving and vehicle_mu_confidence is above 80 with probability 1%.
23/
starfish-ped-bike-motorbike-depth: collects metadata and 3 forward looking cams at 1fps when pedestrians/bikes/... are detected around. 1 data request only.
img-fc-vv-0, img-fc-vv-10 - 1 frame from every camera + metadata, 1 sample each. 24/
that fc-vv stuff has somethingto do with field calibration
depth-sample-lr, depth-sample-rr - only collect some calibration data in case of some depth-percieved objects on any of the cameras. 1 sample each. 25/
occupant-cls-qf: - if you are in gear 4 and the occupant is classified a certain way - collect gps track - one sample

img-lb-weather-rp: if rp camera frame matches a supplied label - collect last right pillar image and coordinates 26/
img-lb-curb: if backup camera maches label collect backup camera latestframe

img-lb-curb-close-rp: if rp image matches label - collect last rp frame

img-lb-over-curb: if backup camera image matches label - colllect lat backup frame

27/
img-lb-over-curb-lr: as above only for left repeater

img-s-rad-hwy-cipv: if following a car and collision warning activated and not on autopilot and speed between 16 and 80 m/s and on controlled access road- collect fisheys, main, and pillar cams 6s video buffer + 1fps 10s buff.
- 3 requests

img-s-rad-local-cipv: as above and we are NOT on controlled acces road - 3 requests

img-vid-don-rand-intervention: 30fps and 10fps video of all cameras if using DoM and disengaged by any method when NOT changing lanes automatically. probability 0.1% - 2 requests
img-vid-don-rand-abort: similar to above - 2 requests (these are VERY large requests at 200+M each)

img-vid-don-ulc-l-diseng: as above only early in ULC left maneuver. 1 request

img-vid-don-ulc-r-diseng: as above only right 1 request 30/
img-vid-don-gore-diseng: DoN aborted and gore zone detected. 2 requests at 0.1% prob.

img-vid-don-steer-diseng: jerking steering wheel above some speed dependent value. 1 request at 0.1% prob. 31/
img-vid-don-brake-diseng: as above only disengage by braking and frontal collision threat asseesnebt if long. acceleration less than 3 m/s^2 1 request at 0.1%

that's the end of the triggers
32/
As you can see - they do collect some elaborate data, but a lot less than many would lead you to believe. And apparently for this reason this knowledge is universally hated by "Bulls" and "bears" alike. 33/
tagging people that touched this topic recently (even though some of them seems to blocked me):

@bobby_tips @FredericLambert @TeslaCharts @brisance @mjd1735 @Paul_M_Huettner @ValueDissenter @quirkyllama @forstall_ @Andreas_Hopf @ContrarianShort @markbspiegel 34/
And no, I have no idea if anybody at Tesla looks at the results, but new triggers do generated frequently and have some variety. No idea how useful the results are either. They are somewhat cautionous with upload sized since storage is not free it looks like.
the data is uploaded to amazon S3 buckets and that bandwidth is not free either I imagine.

Anyway, next time somebody brings the shadow mode or data collection topic - show them this.
Also this is my independent research, I am not am employee of Tesla. Samples available for interested parties.

/FIN

• • •

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

Jan 15
Looks like Model Y heat pumps are seizing en-masse in Russia as well. This is how it looks like:

(in the video they just count start attempts), video credit to some Russian Tesla owners group
When you take the compressor apart you see this

I tried to find a teradown of a working unit, but only can see the outsides of it by Munro. Anybody can link me to the inside views?
In case you cannot tell, these parts are NOT normal, it's the sign of some metal parts hard-rubbing against each other creating this sort of a wear pattern

To me this does not look particularly fixable via OTA.

This might also be fallout from the bad sensors workaround earlier
Read 4 tweets
Dec 21, 2021
Got a pretty worrying #TeslaCrashFootage in the mail.

This is on AP (NoA, really), 75 mph into a truck, no braking, no warnings of any kind.

The firmware is 2021.4.18.2, accident in June 2021.

radar-equipped car (but hw2.5 of course)
the truck was seen by both the radar and also could be clearly observed by the narrow camera from quite a distance away (pictures are spaced 1 second apart)
In fact it was when I reviewed the narrow cam video footage I saw there's a guy with a flashlight behind the truck (I hope they were not hurt and ran away as fast as they could after seeing Tesla not braking)

streamable.com/7ixg7l since twitter likely compressed him out
Read 7 tweets
Aug 25, 2021
USB drive was recovered from this car showing the fire started in the house before jumping to Tesla just as was mostly evident from the outside video
Interesting that (I presume) the owner was in the car and saw everything, escaping out (the car was plugged so cannot even drive it until unplugging.
the drive location in the glove box likely saved it even though it appears to be damaged some
Read 5 tweets
Jul 7, 2021
Holiday weekends are great for some fun are not they?

Worked with @rice_fry on the Tesla depth perception NN.

Remember that stuff in ?

Well, the cars actually have a depth perceiving net inside indeed. though unlike what's shown it's a lot lower res
A whopping 160x120 grid (so 1/8th of the native camera resolution) but hey those are actual 3D points in space. I don't know how to make a 3D video, so just visualizing "distance" as "brighter = closer" on the scale of 5 to 62 meters (the actual limit of the output):
Here's the corresponding time-synced video to better understand what you are looking at.

Pretty cool actually despite all the limitations.
Read 9 tweets
Jul 4, 2021
So in regards to the recent Chinese crash with video where AP exits roadway in sharp turns:
I long planned to do a demo of a similar condition but always forgot and I guess better late than never.
It's actually really easy to reproduce
m.weibo.cn/status/4655186…
Find an (empty!) road with a sharp curve and point autopilot at it. For most safety ensure there's an extra space outside the curve so you can catch the car before it crashes into stuff and boom!
(this is 2021.4.18.3 btw)

Remember to always pay attention when on AP!
If you enable debug mode you see the car actually outputs various alerts before the eventual "take over we are giving up" (weird there was no diseng chime btw)
and it knows it cannot take the turn safely at those speeds, in fact it tries to lower speed but definitely not enough
Read 7 tweets
May 31, 2021
Some more fun with radar-less Model Y (thanks @spleck)

First we laced a brown box with foil (for great radar response) and tested my model X on it (FW 2021.4.18)

It rammed it like nothing, but we did get an FCW.
Internal telemetry view (no radar overlaid because it makes the picture too busy)
One frame from radar view.
From it we learn the box is reported as a vehicle, but existence probability is only 30% and obstacle probability is 60%
Read 6 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 on Twitter!

:(