Connect with us

News

Tesla Full Self-Driving v14.3: First Impressions

Published

on

Tesla started rolling out Full Self-Driving v14.3 to Early Access Program (EAP) members earlier today, and I had the opportunity to see some of the improvements that were made from v14.2.2.5.

While a lot of things got better, and I truly enjoyed using Full Self-Driving again after being stuck with the widely confusing and frustrating v14.2.2.5, Tesla still has one major problem on its hands, and it has to do with Navigation and Routing. I truly believe those issues will be the biggest challenges Tesla will face with autonomy: the car simply going the correct way, not conflicting with what the navigation says, and taking the simplest and most ideal route to a destination.

Here’s what I noticed as an improvement with my first hour with v14.3. This is not a full review, nor is it reflective of everything I will likely experience with this new version. This is simply what I saw as a noticeable improvement from the past version, v14.2.2.5.

There is also a more streamlined version on X, available at the thread below:

Advertisement
-

Yellow Light Behavior is Significantly Better

On v14.2.2.5, I had so many instances of the car slamming the brakes on to stop at a yellow light when it was clearly the safer option to proceed through. There were several times when the car would be about 20 feet from the line, traveling at 15-20 MPH, the light would turn yellow, and it would slam the brakes to stop. I would nudge it through yellow lights constantly because of this by putting my foot on the accelerator.

The instances I’m talking about here would not have been close calls — the car would have likely moved through the intersection completely before the light would turn red.

On multiple occasions this evening, FSD proceeded through yellow lights safely, without hesitation or any brake stabbing. It was refreshing:

This was a huge complaint with v14.2.2.5. Sometimes, it’s a safer option to go through a yellow light, especially when you have traffic behind you. It’s a great way to get rear-ended.

Parking Performance

I had four instances of parking, and FSD v14.3 really did a flawless job. I was very impressed with how solid it was, but also with how efficiently it moved into the spot. When there was traffic around with past versions, I usually chose to park manually just because FSD took its time getting into a spot. I don’t see that being an issue anymore.

I complained about parking a lot and shared several images on X and Facebook of those examples:

Advertisement
-

No issues with it this evening. 4/4. Here are two looks:

Highway Performance

FSD v14.3 passed the five cars shown in this image:

The sixth was 200-300 yards ahead of the fifth. In v14.2.2.5, FSD would usually stay in the left lane, especially on Hurry and Mad Max. It did not do that, as it instead chose to get back over in the right lane after passing the final car.

Speed was not much of a concern here, even though it was going 21 MPH over. Although it was fast, I did have a line of cars behind me traveling at the same speed, and FSD had just merged about a half mile prior, so I chose to let it continue.

There were no instances of camping in the left lane for extended periods of time. I do want to do more testing with the Speed Profiles because they were in need of some work with the previous version. I am starting to side with those who want a Max Speed setting, which was removed last year.

Navigation and Routing Still Need Work

I was heading back toward where I came from, so I turned “Avoid Highways” on to take a different way. This confused the Routing system, and instead of turning left, then right, as the Routing said, the car turned right, then indicated for another right, basically going in a big rectangle. The car ignored the second right-hand turn and continued straight. I ended up turning “Avoid Highways” off and letting the car pick the same routing option as what took me here.

Advertisement
-

I have truly complained so much about Navigation and Routing that I’m starting to feel sort of bad. It is obviously such a massive challenge for some reason, but I am confident it will improve. I recall seeing Tesla hiring someone for this role a few months back, so perhaps there is hope for it to get better.

Smarter Behavior When Approaching Exits/Routing

This probably should be grouped in with Highway Behavior, but I wanted to highlight it on its own.

The highway exit pictured was always frustrating for v14.2.2.5. In the Hurry speed profile, I have seen it try to execute passes on multiple cars with as little as 0.6 miles to spare before taking the exit.

With three cars ahead of it, it chose to reduce speed and just wait until the exit. It was refreshing to see an improvement here, so I hope this behavior persists. Sometimes there’s just no reason to pass when you’re less than a mile from getting off the highway anyway.

Larger Visibility Warnings

Tesla seems to have increased the size of these “Camera Visibility Limited” warnings. Previously, they were just small thumbnails:

Stop Sign Behavior

This is probably the biggest improvement of all, because how it behaved at Stop Signs in v14.2.2.5 was so incredibly terrible and disruptive to the flow of a busy intersection.

There are several four-way, all-stop intersections near me. In the past, FSD would stop well behind the Stop Sign or the white-painted line on the road. It would then inch forward, stopping again at this line, essentially making two stops at a single intersection.

If there is visibility, I don’t truly care where FSD stops, as long as it stops once. Stopping twice just isn’t ideal or logical. I can’t imagine many humans would do it, I know I wouldn’t.

I didn’t have that issue this evening:

Advertisement
-

This was pretty tight, too, in the sense that both my car and the other one got to the intersection at the same time. FSD may have stopped first, but the other vehicle was probably around the same point that I was when FSD decided to stop. I was happy to see the assertiveness to proceed; it felt like it was ideal to just go through. I was happy it didn’t stop a second time up at the line. I’d be fine if it stopped at the line, as long as that was the only stop it made.

Joey has been a journalist covering electric mobility at TESLARATI since August 2019. In his spare time, Joey is playing golf, watching MMA, or cheering on any of his favorite sports teams, including the Baltimore Ravens and Orioles, Miami Heat, Washington Capitals, and Penn State Nittany Lions. You can get in touch with joey at joey@teslarati.com. He is also on X @KlenderJoey. If you're looking for great Tesla accessories, check out shop.teslarati.com

Advertisement
Comments

Elon Musk

Tesla’s Roadster appearance at SpaceX has merger watchers talking

Tesla’s next generation Roadster was spotted at SpaceX’s Hawthorne headquarters, two weeks after its unveiling.

Published

on

By

The Roadster’s rear wing, one of the aerodynamic elements Tesla pairs with a fan-based downforce system. (Image: Tesla)

Tesla’s next generation Roadster turned up at SpaceX’s headquarters in Hawthorne, California on Wednesday, less than two weeks after the car flew off a ramp at its unveiling in Texas.

Photos shared on X by SpaceX Engineer (@DeannaRiceSPCX) show the new Roadster parked outdoors beside the famed Falcon 9 that stands outside company headquarters at the corner of Crenshaw Boulevard and Jack Northrop Avenue. Rocket B1019 was the first orbital-class booster ever to land after a launch on December 21, 2015 after it sent 11 Orbcomm satellites to orbit and then flew back to Landing Zone 1 at Cape Canaveral, which would be the first landing in what became SpaceX’s reusable rocket program. SpaceX chose not to fly it again. After a test fire in Florida, the booster was shipped to Hawthorne and raised upright as a permanent monument in August 2016, as Teslarati reported at the time. Putting the Roadster, which flies on SpaceX cold gas thrusters, next to the rocket that started SpaceX’s landings is symbolic in itself.

The Thrust and Rocket versions of the Roadster use cold gas thrusters fed by composite overwrapped pressure vessels, the same type of tank SpaceX flies on Falcon 9, and Elon Musk described the car as the work of Tesla and SpaceX engineers working together. Tesla lists 0 to 60 mph in under 0.9 seconds for Thrust and under 0.59 seconds for Rocket, while the base Performance model relies on a fan and ground sealing system for grip, as Teslarati detailed in its breakdown of the three Roadster configurations.

Tesla has kept the car in the spotlight since the October 15 event near Waco. Last week, the company posted a video of the Roadster’s fighter jet inspired cockpit, including a Track Mode screen with a “Thruster · 5,500 PSI” readout, which we covered in our look at the Roadster’s center display. Musk also said owners will be able to ask the car to perform the stunts autonomously, and promised a looping track at Tesla’s Texas headquarters.

Advertisement
-

The visit comes as special committees at Tesla and SpaceX weigh a possible merger, a step Musk confirmed on SpaceX’s third quarter earnings call. The Roadster, built on SpaceX hardware, has become one of the clearest examples of the two companies already building products together.

Musk said at the unveiling that Roadster production will begin in 2028. Reservations are open with a $50,000 payment, Thrust is listed as a limited release and Rocket is invite only. Tesla says the car is not approved for public road use.

Continue Reading

News

Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote

AT&T, Verizon and T-Mobile want 290 MHz cut from an FCC satellite plan before Thursday.

Published

on

By

Starlink D2D direct to device vs Verizon, AT&T (Concept render by Grok)

AT&T, Verizon and T-Mobile are asking the Federal Communications Commission to pull nearly 300 MHz of spectrum out of a proposal that would let satellite companies like SpaceX offer cell service directly to ordinary phones. The request lands one day before the agency votes on it.

The FCC will vote Thursday, October 29, on a notice of proposed rulemaking that would make an additional 482 MHz available for direct to device service, expanding the number of eligible bands from five to 13, according to the FCC fact sheet. It would also scrap the rule requiring a satellite operator to lease spectrum from carriers, replacing it with a certification that the operator has coexistence agreements in place or holds the terrestrial license itself.

That second path matters for SpaceX. As Teslarati reported earlier this month, SpaceX agreed to buy Grain Management’s nationwide 800 MHz portfolio to turn Starlink Mobile into a full US carrier, adding to the spectrum it already bought from EchoStar.

The carriers want two bands removed, 2.5 GHz and 3.45 GHz, which make up 290 MHz of the 482 MHz on the table. Through industry group CTIA, they argued that about 300 million users depend on those bands and that satellite operations in them are not technically feasible. T-Mobile, which calls 2.5 GHz the foundation of its Ultra Capacity 5G network, said in its own filing that satellite interference could wipe out up to 96% of a cell site’s uplink coverage area and cut uplink speeds by 88% to 99%.

Executives from all three carriers met with FCC staff on October 20, and T-Mobile CEO Srini Gopalan met separately with FCC Chairman Brendan Carr. T-Mobile’s role stands out because it is still SpaceX’s US launch partner for Starlink Mobile. The three carriers have also teamed up on their own satellite joint venture to pool spectrum, a move widely seen as a response to Starlink.

Advertisement
-

SpaceX is asking for the opposite. In an October 23 filing after meetings with FCC staff and commissioners’ offices, the company asked regulators to add the 902 to 928 MHz band to the proposal. “Doing so now saves time later,” SpaceX wrote. The company also asked the FCC to modernize interference rules and align satellite deployment requirements with those for terrestrial cell networks, saying the goal is to let satellite and ground networks work together so Americans stay connected wherever they are.

The carriers have not been shy about how they view SpaceX as a competitor. On Verizon’s third quarter earnings call Monday, its chief executive said Starlink Mobile “just can’t compete with a terrestrial network” and estimated SpaceX would need four to six years and $300 billion to $500 billion to build a full US carrier network.

Thursday’s vote will not settle which bands survive. Adopting the notice opens a public comment period, with final rules to come later in the proceeding. The FCC already considered and rejected 2.5 GHz for satellite coverage once, in 2024. SpaceX also is not the only satellite player watching: the FCC approved Amazon’s $11.6 billion acquisition of Globalstar on October 27, giving its planned direct to device fleet its own mobile satellite spectrum.

Continue Reading

News

Tesla Semi catches fire in California: what we know

Published

on

Credit: KTVU

A Tesla Semi caught fire in Hayward, California, which caused both directions of traffic to shut down for hours before being completely reopened early on Wednesday, the California Highway Patrol said.

The fire occurred just after 5:30 local time in Hayward on Tuesday, as the Semi caught fire in the southbound lanes of I-880 before CHP officials made the decision to shut down both lanes of traffic due to potential risks from hazardous chemical smoke.

There were no injuries reported.

The cause of the fire is currently unknown, as neither Tesla nor the CHP have not determined a cause.

However, some images taken before the Semi was completely destroyed by the fire seem to indicate this might have been an older unit, as it appears to be one of the designs that Tesla shipped as part of its pilot program, before revising it and starting mass production just a month ago.

At the time of publication, CHP had not returned our request for a comment for additional details, including the Semi involved and any potential collaboration on an investigation between the CHP and Tesla. We will update this story when we hear back from them.

The southbound lanes were reopened at 3:30 a.m. on Wednesday, with the northbound lanes opening last night a few hours after the fire began. The CHP did state that the lithium batteries were “incredibly difficult to extinguish,” according to NBC Bay Area.

The truck’s driver said that the Semi caught fire, but he did not have an explanation.

An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year.

Continue Reading