Then you're good to go.
Tesla HW3: Everything You Need To Know
We check out Tesla's latest hardware, HW3 and explain what it does and how to tell if your Tesla is equipped with it.
insideevs.com
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
insideevs.com
I have no horse left in the race either (had lawyers involved).
For the ones in the race: stop waiting.
dbldwn02
Active Member
What part about MCU1 do you continue to not understand? Its been explained countless times.Then you're good to go.
Tesla HW3: Everything You Need To Know
We check out Tesla's latest hardware, HW3 and explain what it does and how to tell if your Tesla is equipped with it.
Tegra aka MCU1 is not and will never be compatible with FSD. Doesn't matter if you have HW3.0, 4.0, or 52.0...it won't work.
MCU1 has been barely limping along since late 2018 or so anyway. It's time for Tesla to admit that they aren't capable of making MCU1 be usable again, and just upgrade all MCU1 hardware to MCU2, or at least for anybody who paid for FSD. I mean, even if they upgraded every MCU1 car, it would still be less than a quarter million cars in total, and the total real-world manufacturing cost for MCU2 is probably no more than a couple of hundred dollars. For fifty million or thereabouts, the whole problem goes away. That's probably less than the cost of the staff required to make FSD happen on MCU1. And if they do it just for people who bought FSD, it's probably single-digit millions, which is almost definitely less than it would cost for the extra staffing.
dbldwn02
Active Member
Much easier just to ignore it and upgrade the ones who send an official letter requesting it.
I'll give them a couple weeks and then I'll have a lawyer write a strongly worded letter. Time to put the $10/month lawyer subscription to work. I'd recommend everyone else do the same.
And no, I didn't get the lawyer subscription for this...it's for my rental property. Ala carte letter probably run $200.
shanejackson
Member
Just post a copy for everyone to copy with their details…
dbldwn02
Active Member
You and me = same mind-settingJust post a copy for everyone to copy with their details…
And yes I know it's mind-set but a chick in my English class used mind-setting so I try to use it where I can...Money buys degrees
Settle down. People here confuse the FSD computer with the infotainment computer all the time.
Can't you get an upgrade to MCU2? I've read others here get the upgrade, some at no charge and some at cost.
I disagree and have never heard a technical reason why MCU1 wouldn’t work. Now I think it’s possible that FSD Beta never gets released for MCU1, but likely not because it can’t, but rather because the trouble involved in dumbing down, porting the visualizations and testing them is so much work. So when FSD comes out of Beta, do I think Tesla would release an FSD version without the ICU visualizations on MCU1? Maybe. But if they don’t, I don’t think it will be because they couldn’t make it work, I think it would be because they just don’t want to.
I’m sure there are those on this forum that can enlighten us on how HWx takes inputs from the cameras and controls the steering accelerator, regen and braking. Is the MCU really part of that loop? The light input to engage it and modify settings clearly would not strain the Tegra. Do people really think that the Navigation input or some mix of GPS and Nav requirements would overwhelm the Tegra?
I have never heard of anyone getting an MCU2 upgrade for free. HW3? Yes. Cameras? Yes. MCU2? No.
Last edited:
$2000 USD ish. And it’s changed, including depending on whether you needed and/or were entitled to the HW3 upgrade.
Last edited:
Tesomega
Member
6 years ago, Autopilot was in BETA, it currently remains in BETA. Do you think the explanation for why FSD Beta may not work makes sense?
I think the reason FSD Beta doesn’t run on MCU1 is because Tesla doesn’t bother to release a version for it. I think my own explanation makes sense to me. Or are you asking about someone else’s explanation?
I got the hw3 upgrade for free on my 2017 MX but still on MCU1. I would pay for the upgrade to MCU2 except I would have lost FM radio unless I paid an additional fee to get it back!
dbldwn02
Active Member
Got better things to spend $2200 on.
Plus, "all cars built from late 2016 have the required hardware for full self driving" (Tesla Website) So no one who purchased FSD should have to pay another dime to get FSD. Simple.
One challenge is that the visualizations may be considered essential to monitoring the system for safety. And it's not strictly a porting question; there are three computer systems involved with MCU1 instead of two, so it gets a lot more complicated.
The MCU is barely able to handle the camera input from HW3 as it is. With navigate-on-autopilot, there are a lot fewer opportunities for its slowness to cause serious problems than with FSD, where it has to handle a lot more turns in a much shorter period. So the answer is a definite maybe.
Why would FSD care about the camera output from HWx to MCU1 if the core of FSD runs on HWx? Why would the slowness of the MCU cause HWx to be able to make fewer turns?One challenge is that the visualizations may be considered essential to monitoring the system for safety. And it's not strictly a porting question; there are three computer systems involved with MCU1 instead of two, so it gets a lot more complicated.
The MCU is barely able to handle the camera input from HW3 as it is. With navigate-on-autopilot, there are a lot fewer opportunities for its slowness to cause serious problems than with FSD, where it has to handle a lot more turns in a much shorter period. So the answer is a definite maybe.
I could see how there would be more dependence on the MCU if Tesla depended on map data, since the map comes from the MCU. But my understanding is that this data stream is pretty light.
Last edited:
Light or not, the point is that a few seconds of latency makes little difference when you have ten miles to the next exit, but potentially a huge difference if you're turning in 100 feet.
To put this in context, my MCU1 car takes a good half a minute to render a simple zoom change on the map, which tells me that its ability to deal with map data in a timely manner is badly compromised. It has been this way since either the version 9 update in late 2018 or the version 10 update in late 2019. I can't remember which — only that it was at the end of a year, and it was one of the huge updates.
I'm not disagreeing. What has Tesla told you when you asked for the MCU update for FSD?
Similar threads
