Connect with us
starlink-1-4-billion-revenue-spacex starlink-1-4-billion-revenue-spacex

News

SpaceX Starlink Gen2 constellation weakened by “partial” FCC grant

Published

on

More than two and a half years after SpaceX began the process of securing regulatory approval for its next-generation Starlink constellation, the US Federal Communications Commission (FCC) has finally granted the company a license – but only after drastically decreasing its scope.

In May 2020, SpaceX filed its first FCC license application for Starlink Gen2, an upgraded constellation of 30,000 satellites. In the second half of 2021, SpaceX amended its Starlink Gen2 application to take full advantage of the company’s more powerful Starship rocket and further improve the constellation’s potential utility. Only in December 2021 did the FCC finally accept SpaceX’s Gen2 application for filing, kicking off the final review process.

On November 29th, 2022, the FCC completed that review and granted SpaceX permission to launch just 7,500 of the ~30,000 Starlink Gen2 satellites it had requested permission for more than 30 months prior. The FCC offered no explanation of how it arrived at its arbitrary 75% reduction, nor why the resulting number is slightly lower than a different 7,518-satellite Starlink Gen1 constellation SpaceX had already received a license to deploy in late 2018. Adding insult to injury, the FCC repeatedly acknowledges that “the total number of satellites SpaceX is authorized to deploy is not increased by our action today, and in fact is slightly reduced.”

That claimed reduction is thanks to the fact that shortly before this decision, SpaceX told the FCC in good faith that it would voluntarily avoid launching the dedicated V-band Starlink constellation it already received a license for in order “to significantly reduce the total number of satellites ultimately on orbit.” Instead, once Starlink Gen2 was approved, it would request permission to add V-band payloads to a subset of the 29,988 planned Gen2 satellites, achieving a similar result without the need for another 7,518 satellites.

In response, the FCC slashed the total number of Starlink Gen2 satellites permitted to less than the number of satellites approved by the FCC’s November 2018 Starlink V-band authorization; limited those satellites to middle-ground orbits, entirely precluding Gen2 launches to higher or lower orbits; and didn’t even structure its compromise in a way that would at least allow SpaceX to fully complete three Starlink Gen2 ‘shells.’ Worse, the FCC’s partial grant barely mentioned SpaceX’s detailed plans to use new E-band antennas on Starlink Gen2 satellites and next-generation ground stations, simply stating that it will “defer acting on” the request until “further review and coordination with Federal users.”

The FCC’s “partial grant” only allows SpaceX to launch 7,500 of 10,080 Starlink Gen2 satellites meant to operate at altitudes between 525 and 535 kilometers.

Throughout the partial grant, the FCC couches its decision to drastically downscale SpaceX’s Starlink Gen2 constellation in terms of needing more time “to evaluate the complex and novel issues on the record before [the Commission],” raising the question of what exactly the Commission was doing instead in the 30 months since SpaceX’s first Gen2 application and 15 months since its Gen2 modification. In comparison, SpaceX received a full license for its 7,518-satellite V-band constellation less than five months after applying. SpaceX’s 4,408-satellite Starlink Gen1 constellation – the first megaconstellation ever reviewed by the modern FCC – was licensed 16 months after its first application and eight months after a modified application was submitted.

Adding to the oddity of the unusual and inconsistent decision-making in this FCC ruling, the Commission openly acknowledges that the idea to grant SpaceX permission to launch a fraction of its Starlink Gen2 constellation came from Amazon’s Project Kuiper [PDF], a major prospective Starlink competitor. The FCC says it agreed with Amazon’s argument, stating that “the public interest would be served by taking this approach in order to permit monitoring of developments involving this large-scale deployment and permit additional consideration of issues unique to the other orbits SpaceX requests.”

The V-band Starlink constellation already approved by the FCC was for 7,518 satellites in very low Earth orbits (~340 km). In the first 4,425-satellite Starlink constellation licensed by the FCC, the Commission gave SpaceX permission to operate 2,814 satellites at orbits between 1100 and 1300 kilometers. Increasingly conscious of the consequences of space debris, which would last hundreds of years at 1000+ kilometers, SpaceX later requested permission in 2019 and 2020 to launch those 2,814 satellites to around 550 kilometers, where failed satellites would reenter in just five years. For unknown reasons, the FCC only fully approved the change two years later, in April 2021.

Advertisement
-
-

The “other orbits [requested by SpaceX]” that the FCC says create unique issues that demand “additional consideration” of Starlink Gen2 are for 19,400 satellites between 340 and 360 kilometers and 468 satellites between 604 and 614 kilometers. Starlink satellites are expected to be around four times heavier and feature a magnitude more surface area, but the fact remains that the FCC has already granted SpaceX permission to launch almost 3000 smaller satellites to orbits much higher than 604 kilometers and more than 7500 satellites to orbits lower than 360 kilometers. It’s thus hard not to conclude that the Commission’s claims that a partial license denial was warranted by “concerns about orbital debris and space safety,” and “issues unique to…other orbits” are incoherent at best.

SpaceX has already built a significant number of Starlink Gen2 prototypes.

Perhaps the strangest inclusion in the partial grant is a decision by the FCC to subject SpaceX to an arbitrary metric devised by another third-party, for-profit company LeoLabs. In a March 2022 letter, LeoLabs reportedly proposed that “SpaceX’s authorization to continue deploying satellites” be directly linked to an arbitrary metric measuring “the number of years each failed satellite remains in orbit, summed across all failed satellites.” The FCC apparently loved the suggestion and made it an explicit condition of its already harsh Starlink Gen2 authorization, even adopting the arbitrary limit of “100 object years” proposed by LeoLabs.

In other words, once the sum of the time required for all failed Starlink Gen2 satellites to naturally deorbit reaches 100 years, the FCC will force SpaceX to “cease satellite deployment” while it “[reviews] sources of satellite failure” and “determine[s] whether there are any adequate and reliable mitigation measures going forward.” The FCC acknowledges that the arbitrary 100-year limit means that the failure of just 20 Starlink satellites at operational orbits would force the company to halt launches. The Commission does not explain how it will decide when SpaceX can restart Starlink launches after a launch halt. SpaceX must simultaneously follow the FCC’s deployment schedule, which could see the company’s license revoked if it doesn’t deploy 3,750 Starlink Gen2 satellites by November 2028 and all 7,500 satellites by November 2031.

Based on the unofficial observations of astrophysicist Jonathan McDowell, SpaceX currently has more 30 failed Starlink Gen1 satellites at or close to their operational altitudes of 500+ kilometers, meaning that SpaceX would almost certainly be forced to stop launching Gen1 satellites if this arbitrary new rule were applied to other constellations. The same is true for competitor OneWeb, which had a single satellite fail at around 1200 kilometers in 2021. At that altitude, it will likely take hundreds of “object years” to naturally deorbit, easily surpassing LeoLabs’ draconian 100-year limit.

In theory, the FCC does make it clear that it will consider changing those restrictions and allowing SpaceX to launch more of its proposed Starlink Gen2 constellation in the future. But the Commission has also repeatedly demonstrated to SpaceX that it will happily take years to modify existing licenses or approve new ones – not a particularly reassuring foundation for investments as large and precarious as megaconstellations.

Ultimately, short of shady handshake deals in back rooms, the FCC’s partial grant leaves SpaceX’s Starlink Gen2 constellation in an undesirable position. For the company to proceed under the current license, it could be forced to redesign its satellites and ground stations to avoid the E-band, or gamble by continuing to build and deploy satellites and ground stations with E-band antennas without a guarantee that it’ll ever be able to use that hardware. There is also no guarantee that the FCC will permit SpaceX to launch any of the ~22,500 satellites left on the table by the partial grant, which will drastically change the financial calculus that determines whether the constellation is economically viable and how expansive associated infrastructure needs to be.

Additionally, if SpaceX accepts the gambit and launches all 7,500 approved Gen2 satellites only for the FCC to fail to approve expansions, Starlink Gen2 would be stuck with zero polar coverage, significantly reducing the constellation’s overall utility. Starlink Gen2 likely represents an investment of at least $30-60 billion (assuming an unprecedentedly low $1-2M to build and launch each 50-150 Gbps satellite). With its partial license denial and the addition of several new and arbitrary conditions, the FCC is effectively forcing SpaceX to take an even riskier gamble with the billions of dollars of brand new infrastructure it will need to build to manufacture, launch, operate, and utilize its Starlink Gen2 constellation.

Advertisement
-
-

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla briefly offered this Robotaxi part for your personal car

Published

on

Credit: @tpgoebel | X

Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.

Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.

First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.

This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.

However, this part has since been removed and is no longer visible on the EPC.

Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?

While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.

AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.

This could be the first hint of that’s where we are headed.

Continue Reading

News

Tesla Robotaxi gets sweeping but polarizing change

Published

on

Credit: Tesla

Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.

Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.

But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:

However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.

Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.

Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.

The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.

Continue Reading

News

Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots

Published

on

Credit: Tesla

Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.

Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.

However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.

With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.

Turning Hesitancy, Inaccuracy

I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.

Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.

I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.

FSD Disregards Manual Turn Signals

This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.

If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.

FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.

This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.

This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.

Bird Braking is a Thing of the Past

The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.

There have been zero issues with this so far in v14.3.6, which is an excellent improvement.

FSD Might Already Be Taking Note of Driver Preferences

Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.

This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.

Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.

Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.

It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.

As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.

Continue Reading