Connect with us

News

SpaceX settles on Thursday for first Falcon 9 launch of 2021

After a few days of delays, Falcon 9 booster B1060's fourth flight is on track to be SpaceX's first launch of the new year. (Richard Angle)

Published

on

After a few days of delays, SpaceX appears to have settled on Thursday, January 7th for the first of several dozen Falcon 9 launches planned in 2021.

Originally scheduled to launch as early as January 4th, SpaceX’s Turksat 5A communications satellite launch was “placed TBD due to mission assurance” on January 1st – an unfortunate catch-all euphemism often used by launch providers in lieu of any real explanation for delays. Regardless, Next Spaceflight reports that Turksat 5A will be Falcon 9 B1060’s fourth launch, a milestone the first stage (booster) has reached just six months after its first flight.

Despite the minor delay, SpaceX’s current target of four launches this month is still well within reach even though the slip exemplifies the uphill battle the company will face as it aims to achieve CEO Elon Musk’s goal of 48 launches in 2021. Weather is currently 60% favorable for SpaceX’s first launch of the year and Turksat 5A is scheduled to lift off no earlier than 8:28 pm EST on January 7th (01:28 UTC, 8 Jan).

Unfortunately, SpaceX’s first launch of the new year has been steeped in unprecedented controversy for the company, including the first-ever instance of mass-protests at its Hawthorne, California factory and headquarters. The reason: Turksat 5A, while partially meant for civilian communications, will also support the Turkish military, which supported Azerbaijan after the country – unprovoked – reignited a long-simmering conflict in the Nagorno-Karabakh region in September 2020.

Stemming from events that transpired over the last several centuries, Armenian-Azeri conflict and Turkish involvement are extraordinarily complex and messy. In the 1910s and 1920s, Turkey (then the Ottoman Empire) infamously committed atrocities against Armenian, Assyrian, and Greek communities within its occupied territory in a process of “Turkification”, systematically killing 1-3 million people in what would ultimately be labeled genocide. In a separate but related conflict, Turkey eventually chose to support Azerbaijan’s claim to the ethnically (75-90%) and historically Armenian territory, backing the country against Armenia in the first Nagorno-Karabakh War in the 1990s.

Azerbaijan reignited the conflict in 2020, resulting in the deaths of at least 6000 combatants and civilians on both sides and ultimately securing a substantial portion of Nagorno-Karabakh territory as part of a November 2020 ceasefire agreement. To an extent, Nagorno-Karabakh’s borders are now more or less back to where they were before the first war in the 1990s. While an avoidable loss of life is inherently deplorable, it’s extremely difficult to say whether Azerbaijan was justified but it and Turkey’s history of systematic and discriminatory hostility towards Armenians leaves little benefit of the doubt worth giving.

Ultimately, that cloud of ambiguity makes it hard to directly fault SpaceX for choosing to launch Turksat 5A or for its contracts to launch Turksat 5B and future domestically-built satellites. Additionally, if SpaceX should be criticized for willingly launching the satellite, Airbus – contracted by Turkey to build Turksat 5A – is at least as worthy of critique but has yet to be included at all in protest discourse despite the fact that Turkey’s production contract was publicly announced in 2017.

Advertisement
-
-

In the history of spaceflight, a satellite that is completed but never launches is all but unheard of, as the inherent bureaucratic and financial inertia behind a launch campaign mere months away from its scheduled liftoff is obviously immense. Even if SpaceX were to accept major financial penalties and back out of its contract, Arianespace, Roscosmos, or ULA would assuredly accept any replacement contract.

For protestors still set on making an impact, the shrewd move would be to redirect attention on future Turkish satellite projects like Turksat 5B, 6A, and beyond with the intention of killing contracts in the cradle – a far more tenable goal.

Stay tuned for more launch details as SpaceX nears its first mission of 2021.

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 silences Robotaxi turn signals in 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

Elon Musk

Musk’s massive Terafab project will get final location soon

Published

on

Credit: SpaceX

Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.

“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.

Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry

Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.

The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.

In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.

However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.

Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.

Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.

“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”

He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”

Continue Reading