Cybertruck source code

Tinker71

Well-known member
First Name
Ray
Joined
Aug 8, 2020
Threads
82
Messages
1,484
Reaction score
1,967
Location
Utah
Vehicles
1976 electric conversion bus
Occupation
Project Manager
Country flag
We all read the stories about the computer sleuths finding tidbits of information on the new Tesla models or features before they roll out. If I recall there are already hints about the CT with some off-road sensors etc.

What go me wondering about all this was the potential model line up for CT. At some point managing the code for the soon to be millions of Teslas for their 15+ year lifespans might be difficult and overhead intensive and this might become a determining factor in model variation going forward.

Does Tesla have a single base code for all models produced? How much of the CT code will be shared with the Y? It appears to me there are already 1000's of combinations of motors, batteries, heat pumps, seat controls etc. in the Tesla fleet. It is fairly obvious each build series have it's own inputs or variables which would be fairly easy to manage in itself. So not every model gets its own unique code.

Things like FSD subscriptions even access to extra power can be turned on remotely without a complete wipe and upload of code if not mistaken. Torque vectoring will probably be a fundamental change to the code. Will it be in the code for all models and turned on/off with a program switch, or will all models with torque vectoring get separately managed software version?
Sponsored

 

CyberGus

Well-known member
First Name
Gus
Joined
May 22, 2021
Threads
67
Messages
5,807
Reaction score
19,082
Location
Austin, TX
Website
www.timeanddate.com
Vehicles
1981 DeLorean, 2024 Cybertruck
Occupation
IT Specialist
Country flag
PC operating systems function across many different manufacturers and platforms, with thousands of accessories. Apple manages to use the same core OS across their product lines (Desktop, laptop, phone, tablet) and 3 different CPUs (PowerPC, Intel, and RISC).

Tesla controls the software and hardware. They've got it easy.
 

Crissa

Well-known member
First Name
Crissa
Joined
Jul 8, 2020
Threads
126
Messages
16,211
Reaction score
27,072
Location
Santa Cruz
Vehicles
2014 Zero S, 2013 Mazda 3
Country flag
We all read the stories about the computer sleuths finding tidbits of information on the new Tesla models or features before they roll out. If I recall there are already hints about the CT with some off-road sensors etc.
Does Tesla have a single base code for all models produced? How much of the CT code will be shared with the Y? It appears to me there are already 1000's of combinations of motors, batteries, heat pumps, seat controls etc. in the Tesla fleet. It is fairly obvious each build series have it's own inputs or variables which would be fairly easy to manage in itself. So not every model gets its own unique code.
Yes, one code to rule them all.

They have a limited number of computer core revisions, which makes this easier. But this is one reason why they keep the variation in models as simple as possible - because they do need to make firmware and test compatibility with thousands of components.

FSD is really where things will get sticky, as the Cybertruck will 'see' the world and physically be much bigger. It may need its own FSD stack.

-Crissa
 

flowerlandfilms

Well-known member
First Name
Eryk
Joined
Dec 6, 2020
Threads
5
Messages
790
Reaction score
1,679
Location
Australia
Vehicles
Yamaha SRV-250, Honda Odyssey RB1
Occupation
Film Maker
Country flag
Yes, one code to rule them all.

They have a limited number of computer core revisions, which makes this easier. But this is one reason why they keep the variation in models as simple as possible - because they do need to make firmware and test compatibility with thousands of components.

FSD is really where things will get sticky, as the Cybertruck will 'see' the world and physically be much bigger. It may need its own FSD stack.

-Crissa
Yeh, I have been wondering how that will work, especially if it ends up with more or differently placed cameras.
I have a lot of questions for Andrej Karpathy that no one ever seems to ask.
Like if FSD visualisations will always look like an episode of Dr. Katz.

Tesla Cybertruck Cybertruck source code dr-katz-title-shot
 

Crissa

Well-known member
First Name
Crissa
Joined
Jul 8, 2020
Threads
126
Messages
16,211
Reaction score
27,072
Location
Santa Cruz
Vehicles
2014 Zero S, 2013 Mazda 3
Country flag
Yeh, I have been wondering how that will work, especially if it ends up with more or differently placed cameras.
I have a lot of questions for Andrej Karpathy that no one ever seems to ask.
Like if FSD visualisations will always look like an episode of Dr. Katz.

dr-katz-title-shot.gif
Well... Yes and yes. The squiggle-vision is from the uncertainty of shifting pixels and predictions of the models. Computationally, it's like seeing stuff in your peripheral vision. Every frame comes up just slightly different - just like the hand-drawn lines that squiggle-vision is mimicking.

And Tesla had been testing a Model 3 with a roof-rack and cameras hung on it in a different heigh and configuration. Best guess was it a rig to give them a model to teach FSD what it looked like from a Cybertruck or Semi point of view.

-Crissa
 


flowerlandfilms

Well-known member
First Name
Eryk
Joined
Dec 6, 2020
Threads
5
Messages
790
Reaction score
1,679
Location
Australia
Vehicles
Yamaha SRV-250, Honda Odyssey RB1
Occupation
Film Maker
Country flag
Well... Yes and yes. The squiggle-vision is from the uncertainty of shifting pixels and predictions of the models. Computationally, it's like seeing stuff in your peripheral vision. Every frame comes up just slightly different - just like the hand-drawn lines that squiggle-vision is mimicking.

And Tesla had been testing a Model 3 with a roof-rack and cameras hung on it in a different heigh and configuration. Best guess was it a rig to give them a model to teach FSD what it looked like from a Cybertruck or Semi point of view.

-Crissa
Surely you could write an algorithm which smooths out the lines and gives them persistence though? Even if it's not 100% accurate to what the computer sees. Maybe for the final product when aesthetics and consumer confidence is more of a consideration. It's fascinating seeing the computer "perceive" either way.
 

Dids

Well-known member
First Name
Les
Joined
Dec 21, 2019
Threads
8
Messages
1,766
Reaction score
3,771
Location
Massachusetts
Vehicles
04 Tacoma, 23 Cybertruck
Occupation
Self
Country flag
Surely you could write an algorithm which smooths out the lines and gives them persistence though? Even if it's not 100% accurate to what the computer sees. Maybe for the final product when aesthetics and consumer confidence is more of a consideration. It's fascinating seeing the computer "perceive" either way.
That seems like such a waste of time. The display is for debugging it isn't intended for consumers.
 
OP
OP
Tinker71

Tinker71

Well-known member
First Name
Ray
Joined
Aug 8, 2020
Threads
82
Messages
1,484
Reaction score
1,967
Location
Utah
Vehicles
1976 electric conversion bus
Occupation
Project Manager
Country flag
Yes, one code to rule them all.

They have a limited number of computer core revisions, which makes this easier. But this is one reason why they keep the variation in models as simple as possible - because they do need to make firmware and test compatibility with thousands of components.

FSD is really where things will get sticky, as the Cybertruck will 'see' the world and physically be much bigger. It may need its own FSD stack.

-Crissa
Thanks Crissa. My high school coding from the late 80's foresees lots of REM statements?? or the not DOS equivalent :)
Maybe every 10 years or so they will clean up the cores for obviously obsolete features or sections of code.

I looked up the respective lengths of the line up, I was surprised how tight the range is between the 3 and the X (only 16"). The CT might be a full 32" longer.

A separate core would might make sense for the CT with all the off-road capabilities, H4.0 chipset, size, heavy towing, heavy payloads, air suspension etc.

The whole over the air updates process is intriguing with testing, revision control, reversing some changes. I get annoyed by my Android updates changing the look of stuff on my phone and constantly scheduling updates. I guess most Tesla drivers are more used to rapid change.
 

Crissa

Well-known member
First Name
Crissa
Joined
Jul 8, 2020
Threads
126
Messages
16,211
Reaction score
27,072
Location
Santa Cruz
Vehicles
2014 Zero S, 2013 Mazda 3
Country flag
Surely you could write an algorithm which smooths out the lines and gives them persistence though? Even if it's not 100% accurate to what the computer sees. Maybe for the final product when aesthetics and consumer confidence is more of a consideration. It's fascinating seeing the computer "perceive" either way.
Then you miss the frames.

Persistence is a problem in computer ai vision, but they're working on it.

Anyhow, what it'll show to the end user will be highly simplified.

The new machine learning being what it is, when they build a new stack it 'teaches' itself from the label data all pver again. Hence Dojo. Each iteration is faster, simpler, but each time they try to teach it to balance between tasks, it gets more complex.

https://en.wikipedia.org/wiki/AlphaGo

Tesla is trying to follow this path.

-Crissa
Sponsored

 
 




Top