Kalakshar US

ispace is done analyzing data from its failed Hakuto-R lunar landing, and it sounds like tricky terrain and a late change in the landing site are to blame. Apparently, Hakuto-R was able to complete the whole deceleration process in preparation of touching down on lunar soil. The spacecraft activated its descent sequence when it reached an altitude of around 100 kilometers (62 miles) and was able to slow down until it was only moving at a speed of less than 1 m/s. 

However, its software had mistakenly estimated its altitude to be zero when it was still hovering around 5 kilometers (3 miles) above the ground. In other words, it thought it had already landed when it hasn’t yet, and it continued descending at a very slow speed near the surface until its propulsion system ran out of fuel. ispace wasn’t able to establish contact with the spacecraft again, but it believes it went on a free fall and ultimately crashed on the moon.

That’s the how, but what about the why? Well, the company thinks the most likely reason why Hakuto-R’s software suffered from an altitude estimation issue was because it got confused. While it was flying to its landing site, it passed over a large cliff that was determined to be the rim of a crater. The spacecraft’s onboard sensor got an altitude reading of 3 kilometers when it passed by the elevated terrain, and that was apparently larger than the estimated altitude value the Hakuto-R team set in advance. 

The spacecraft’s software erroneously thought that the sensor reported an abnormal value, and it kept filtering out its altitude measurements afterward. ispace built the ability to reject abnormal altitude measurements into the lander as a safety measure in the event of a hardware issue with the sensor. However, it backfired for Mission 1 because simulations of the landing sequence failed to incorporate the lunar environment on the spacecraft’s route. ispace made the decision to change Hakuto-R’s landing site after its critical design review was already completed in 2021. 

The Hakuto-R Mission 1 was poised to become the first successful moon landing by a private company and the first Japanese lunar landing overall. While it didn’t get to land on the moon, ispace will use the data from the mission to design preparatory landing sequences for Mission 2 and 3, which are scheduled for launch in 2024 and 2025, respectively. 

This article originally appeared on Engadget at https://www.engadget.com/japans-ispace-says-hakuto-r-crashed-because-it-got-confused-by-a-crater-rim-113115803.html?src=rss 

We can all agree that robocalls are the worst. While there might never be a way to get rid of them entirely (though agencies are certainly working on it), one the most prolific sources of these intrusions is finally getting hauled into court.

CBS News reports that Attorneys General from 48 states (as well as DC) are coming together to file a bipartisan lawsuit against Arizona-based Avid Telecom, its owner Michael D. Lansky and vice president Stacey S. Reeves. The 141-page suit claims that the company illegally made over 7.5 billion calls to people on the National Do Not Call Registry. Arizona Attorney General Kris Meyes claims that nearly 197 million robocalls were made to phone numbers in her state over a five-year period between December 2018 and January 2023.

The lawsuit says that Avid Telecom spoofed phone numbers, including 8.4 million that appeared to be coming from the government or law enforcement, and others disguised as originating from Amazon, DirecTV and many more. The suit alleges that Avid Telecom violated the Telephone and Consumer Act, the Telemarketing Sales Rule and several other telemarketing and consumer laws. 

The AGs are asking the court to enjoin Avid Telecom from making illegal robocalls, and to pay damages and restitution to the people it called illegally. They’re also pursuing several statutory avenues to make Avid cough of money on a per-violation basis, which given the enormous volume of calls it has made, could add up quickly. Sumco Panama, which was responsible for a comparatively smaller 5 billion robocalls, was fined nearly $300 million by the FCC late last year.

Earlier this month, it was reported that XCast Labs is being sued by the U.S. Federal Trade Commission over allegedly helping other companies call those on the National Do Not Call Registry.

In 2017, Dish reached a settlement that cost them $210 million. The company allegedly made millions of calls in an attempt to sell and promote its satellite TV service. Dish ultimately had to pay a $126 million civil fine to the US government, and $84 million to residents in California, Illinois, North Carolina and Ohio. Hopefully, we’ll see a similar result with Avid Telecom.

This article originally appeared on Engadget at https://www.engadget.com/company-responsible-for-75-billion-robocalls-sued-by-nearly-every-attorney-general-220050450.html?src=rss