Why FSD differs between cars

Documented mechanism

Tesla’s Model Y manual describes cameras around the vehicle feeding a model of the surrounding area. It says the installed AI computer processes neural networks and makes driving decisions. Those are the documented ingredients. The three-layer diagram above separates hardware, installed software and regional availability; it is not a schematic of the proprietary network layers or a claim about how many networks a given release contains. [5]

Engineering model

As a general engineering model, an assisted-driving system must connect sensing to a representation of the scene, a choice of motion and commands to the vehicle. Errors can arise at each boundary: an object may be obscured, its motion may be uncertain, or a planned manoeuvre may become unsuitable as traffic changes. This model helps explain limitations without pretending Tesla has published a fixed perception/planning/control architecture for every release.

Owner check

Identify the installed computer through the touchscreen rather than relying on model year or the appearance of a camera lens. Tesla’s support instructions point to Controls, Software and Additional Vehicle Information. Its computer-upgrade page describes a particular 2.0/2.5-to-3.0 programme; that is not documentation of universal eligibility for a different retrofit. Hardware labels in the tracker should be read alongside the vehicle’s own configuration. [4]

Explanation

The engineering reason hardware matters is that running a model has finite memory, computing, thermal and input/output requirements. A software update can change what is computed, but it does not physically add a new camera or replace a processor. That general constraint does not establish which future Tesla release can run on which vehicle. Claims about memory bandwidth, chip performance or upgrade dates need a specific primary specification or dated announcement; a hardware number is not enough to infer them.

How to read tracker data

A vehicle build identifies an installed software package. An FSD version identifies a driving-software release. Trackers may report both, along with hardware and market. Treat the values as labels to match with release notes, rather than decimal numbers: a version string is not a measurement of intelligence, and a larger-looking suffix does not prove that every feature is newer or available on every branch. [3]

Explanation

A useful comparison keeps five fields together: computer hardware, vehicle build, FSD version, entitlement and region. If one is missing, say so. The table in this lesson shows reported branches from the maintained tracker; it deliberately does not invent a yes/no capability matrix from version names. Its snapshot date records the data, while the reference-review date records when the explanation was checked.

Documented behaviour

Tesla says updates arrive on a rolling basis. Two apparently similar cars can therefore be on different builds at the same time. Advanced requests updates as they become available for that configuration and region; it is not a promise of immediate access to every new release. A tracker’s first observation establishes that a sample received a build, not that an entire fleet is eligible. [7]

Owner check

Download and installation are separate states. The Model Y manual says software can download before installation, and the car cannot be driven while installation is taking place. It also says Advanced does not enrol the vehicle in the early-access programme. After installation, read the release notes on the car: they describe that installed package and may contain feature-specific instructions. [8]

Explanation

This explains a common apparent contradiction: a website can correctly report a release while your car correctly reports that it is up to date. Those statements concern different scopes. The useful next step is to identify the installed build and review official availability information, rather than treating a sample count or an enthusiastic owner post as an update guarantee.

Vehicle-specific fact

The cited US Model Y chapter lists a front-bumper camera, a rear camera, one in each door pillar, two at the windshield and one on each front fender: eight road-facing cameras in that configuration. The cabin camera is separate. This inventory belongs to that manual, rather than every Tesla carrying an HW4 label. [6]

Vehicle-specific fact

The US Model Y camera chapter gives a typical calibration distance of 20–25 miles, or 32–40 kilometres, while noting that conditions change the result. It describes calibration as necessary before certain assistance and active-safety functions can first become available, and after some service work. A progress indicator is evidence about calibration status; it is not a general confidence score for every future driving situation. [9]

Explanation

Visibility matters after calibration too. The manual identifies obstructions and environmental conditions as performance limits. A clear lens cannot reveal something hidden behind another vehicle, and an illustration of a camera cone is not a certified coverage envelope. Separate a dirty or blocked camera, incomplete calibration and an ambiguous traffic scene when diagnosing a limitation: they describe different causes, even if the driver ultimately has to take over. [6]

Explanation

The cabin-facing camera has a different job from road-facing cameras. Tesla’s FSD chapter describes it monitoring driver attentiveness while supervised driving is engaged. Watching the driver does not remove the driver’s responsibility to watch the road. Use the manual for the exact configuration and region; assistance naming and available controls can change with software. [5]

Explanation

A route video can document one journey under particular conditions. It does not, without a denominator and a test protocol, establish the probability of a safe outcome across weather, road layouts and interventions. To compare two demonstrations, ask whether the route, traffic, driver input, hardware, software and editing are comparable. A montage of smooth turns is different evidence from an independently specified test.

Responsibility and scope

NHTSA distinguishes momentary warnings/interventions from continuous assistance. A system that performs steering and speed control while the human remains responsible belongs to a different category from a vehicle that can operate without that human role. Tesla’s consumer FSD support material continues to require active supervision. Automation terminology should describe the responsibility and operating conditions, not how impressive a single manoeuvre looks. [2] [1]

Explanation

For a feature claim, prefer the car’s release notes and manual, then a dated official announcement with its hardware and region. Owner reports are useful observations when labelled as such. They can establish that a particular owner reported an event; they cannot automatically establish a universal rollout, an internal design detail or a future upgrade commitment. This is why the lesson connects to the live tracker instead of freezing a list of promises into the artwork.