Recommended Posts

three weeks later after everyone has dispersed and the field has settled down.........

 

post-546174-0-61203200-1434061718.jpg

 

2 extra shots...hard landing...

 

post-546174-0-19650100-1434062151.jpg

 

back home...

 

post-546174-0-60585800-1434062183.jpg

 

 

  • Like 1

yeah Sam is awesome. If you look on the ESA youtube page she has posted a lot of videos and they recently also did a 3D tour of the Columbus Module.

 

http://www.esa.int/Our_Activities/Human_Spaceflight/International_Space_Station/Highlights/International_Space_Station_panoramic_tour

 

That is the link to the 3D tour of the Columbus Module. You can click on the Red Circles on it to get more information and even links to a few of Sam's Videos.

  • Like 1

Today's news.......

 

This video is of the departure of the capsule...it actually shows how the docking adapter works and shows the separation......good video...

 

Expedition 43 welcomed home....

 

And it would't be a good day unless I posted something..........different.........."SpaceSquatch".............. :woot:

 

post-546174-0-49437900-1434211480.jpg

 

http://www.space.com/29658-astronaut-statues-invade-seattle-museum-art.html

 

 

 

Ah right I understand more now how the latch system works I always wondered how they removed the spike [if I might call it that] used to latch onto the station

Pretty neat eh!......cheers

  • Like 1

The Bigelow expandable module will be launched on a SpaceX Falcon 9 v1.1 to the ISS this year..TBA......So here is a bit of info on the unit....

 

Video showing design and use...

 

Picture of packed unit for launch...

post-546174-0-93805700-1434223094.jpg

 

Prototype space station....

post-546174-0-83926800-1434223137.jpg

 

and an infographic......

post-546174-0-25796500-1434223207.jpg

 

http://spaceref.biz/company/bigelow/2015-could-be-a-milestone-year-for-bigelow-aerospace.html

 

http://www.space.com/28855-inflatable-space-station-habitat-bigelow.html

 

http://www.parabolicarc.com/2015/03/12/54848/

 

BEAM goes up on CRS-8, currently scheduled for September 2.

BEAM 2 will be equipped for use as an EVA airlock on Bigelow's Alpha Station propulsion/docking module. Prop/docking module at left in the photo & BEAM 2 in the patent drawing at the bottom. BEAM 2 is already under construction.

yru3yhaj.jpg

US20120318926A1-20121220-D00000.png

  • Like 1

Is there much difference in landing force of the Russian technique of solid ground with boosters versus the US water and parachute type and whats the advantage and disadvantages of both?

It depends on the spacecraft.

The Soyuz single parachute landing comes down at about 7.2 m/s then the solids fire for a 1.5 m/s touchdown, but on some flights the solid landing rockets have failed resulting in a hard landing and injuries. Astronauts have described this as like being in a car crash.

Soyuz then falls over on its side, or rolls down a hill, but the real excitement has come when it has overshot the landing zone and gone into a body of water. Soyuz 23 landed on a frozen lake, which . didn't go particularly well. The parachute filled with water, causing the escape hatch to be submerged. They weren't found until the next day.

A nominal US Orion water splashdown is at 7.6 m/s, and at worst about 11 m/s with only 2 parachutes open. The harnesses holds the spacecraft so the lower edge slices into the water for a much softer splashdown.

Dragon 2's 3 parschute water splashdown is at 4.9 m/s, a lot gentler, and it too lands lower edge first to further soften the solashdown.

Dragon 2's Soyuz-style 3 parachute landing fires the SuperDraco liquid thrusters at about 10 meters, then it comes to a near hover before gently settling on its 4 legs. Like a helicopter.

Full propulsive Dragon 2 landings (no parachutes) would start the SuperDracos at about 7,000 feet at low throttle and decelerate to also do a helicopter style landing.

If the SuprrDraco engines don't fire properly at 7,000 feet the parachutes are a backup and Dragon 2 can do a land touchdown without them. It would come down on the rear legs first then settle on the front legs.

Yup. Dragon 2 has four landing modes.

What happens with these inflatable modules if they get pierced by micro-metrorites or debris?

They're actually expandable rather than inflatable. Inflatable hints at a balloon which they really aren't. The Bigelow station modules have a wall thickness of .4 to .45 meter and they have a metal core.

NASA tests proposed ISS module designs by firing up to a 17 mm metal sphere at them at a velocity of 7,000 m/s (15,600 mph) using their (totally outrageous) Hypervelocity Gun.

Your typical ISS module wall ends up with an 8-10 cm hole blasted through most of its metal & fabric layers, usually stopping at the last layer.

The Bigelow module wall stopped the projectile cold in its outer layers, and it remained airtight. They kept trying but ended up breaking not the module wall but the Hypervelocity Gun.

  • Like 1

Better yet, because its mostly hydrogen-rich polymers the structure is a good radiation shield. For the DS (deep space) versions they can add water layers to enhance the shield. Add a boron compound to the water layers and it's a good neutron shield too.

  • Like 1

So much for a smooth Soyuz landing....

http://www.spacedaily.com/m/reports/Hard_landing_as_three_astronauts_return_to_Earth_from_ISS_999.html

'Hard landing' as three astronauts return to Earth from ISS

By Anna SMOLCHENKO

Moscow (AFP) June 11, 2015

>

Both Russian mission control and NASA reported no glitches, but Shkaplerov, the commander of the Soyuz spacecraft, said their landing was "hard and quick."

"For some reason, we were spinning," he said in comments broadcast on national television and cited by Russian journalists. No other details were provided.

The 43-year-old cosmonaut added however that "everything worked accurately."

>

DocM...you are right...check out the pictures I posted...one was a bad flare...the other was a very large dust cloud...if it wasn't for the form fitting seats, someone may have had a back injury.....Cheers..

 

Found it...

post-546174-0-72242300-1434252755.jpg

 

We have talked about space junk, micro meteoroids, frozen loose materials but not asteroids. Well, they are not really an issue yet due to the low earth orbit but we do have the occasional shower, about a dozen a year, a lot of which are predictable and if an issue arises, the station can lower or raise position. Drills are held for such an event with spare oxygen tanks, and a getaway vehicle if needed. The ISS is the size of a football field with solar panels of approximately one acre. This would be more likely, by area, than the station itself, which has a small cross section. But...stuff happens....

 

While talking about flying large rocks...we have asteroids of many sizes and some traveling at amazing speeds...some are deemed near earth objects that need attention....NASA has an updated list so you can see what disaster is in the making.......(joking...I think...you decide)

 

http://neo.jpl.nasa.gov/ca/

 

Asteroid naming conventions....There are strict rules on naming. Once one is found, it is given a place holder number and the red tape begins...they generally require standard for the naming but you can put in suggestions...general rules....

 

 

 

When an asteroid is first discovered, it is given a provisional designation like "1999 RQ36."  The first four digits tell you what year it was discovered.  The last four characters tell you when in that year it was discovered. 1999 RQ36 was the 916th object observed in the first half of September, 1999.

Once the asteroid's orbit is precisely known, it is issued an official sequential number.  1999 RQ36 was the 101,955th asteroid to receive a number, so it is now formally known as 101955. Only about 5% of numbered asteroids have been given names.

When asteroids are discovered, they are initially named with numbers and letters encoding when they were first spotted.  The Minor Planet Center at the Smithsonian Astrophysical Observatory gives them these alphanumeric codes.

The asteroid's discoverer can propose to the International Astronomical Union to give the asteroid a formal name.  The International Astronomical Union has established rules to guide the selection of names for objects located in different parts of the solar system.  Here are the guidelines for naming (101955) 1999 RQ36:

Proposed names must be:

no more than 16 characters long (including any spaces or punctuation);
preferably one word;
pronounceable (in some language);
written using Latin characters (transliterations of names from languages not written using Latin characters are acceptable);
non-offensive;
not identical with or even too similar to an existing name of a minor planet or natural planetary satellite.
In addition, because (101955) 1999 RQ36 is a near-Earth object, its name should be from mythology, but the name should not be one associated with creation or underworld themes because those themes are used for other types of bodies in the solar system. The mythological name can come from any culture from any part of the world. In very rare cases, this definition has been stretched to include fictional mythological characters. There are some exceptions to these rules, and entries of names that are not mythological will not be disqualified. However, the International Astronomical Union is likelier to approve a name that is from mythology than one that is not.

http://www.planetary.org/get-involved/contests/osirisrex/guidelines.html

 

The reason I chose this topic was because of a very special naming.....

 

post-546174-0-48361900-1434333782.jpg

 

 

The legacy of Leonard Nimoy has reached the Final Frontier: on June 2, a 6-mile-wide (9.6 km) asteroid was named 4864 Nimoy in his honor. The asteroid travels within the main asteroid belt

  • Like 1

DocM...you are right...check out the pictures I posted...one was a bad flare...the other was a very large dust cloud...if it wasn't for the form fitting seats, someone may have had a back injury.....Cheers..

 

Found it...

attachicon.gifTMA15M.jpg

 

Wow. Hard landing indeed ... glad they're all okay. Spinning and a hard landing indicates they came in a little hot .. not something you want on a ground-based capsule landing that isn't using much in the way of impact absorption.

 

I've been a big fan of Soyuz over the years, but I'm starting to rethink my position. Yikes. Too many problems lately.

  • Like 1

Which is why the Commercial Crew Program is so important. So much has come out of it for relatively low cost as compared to other programs. This is why it is so easy to pick out the "corruptables in the House and Senate". Common sense will dictate and we know what will happen when a "death" occurs due to short sightedness.....Cheers...... :)

  • Like 1

I think even if the CCP gets blown out, SpaceX will continue on. It's not like they need the permission of the U.S. Government, or (really) the money anymore. Not with the success they've already had. Dragon 2 is almost ready for flight, and the hard parts in its' Dev Cycle are finished. They'll have plenty of customers, including the U.S. Government if everything goes to plan.

  • Like 1

I think even if the CCP gets blown out, SpaceX will continue on. It's not like they need the permission of the U.S. Government, or (really) the money anymore. Not with the success they've already had. Dragon 2 is almost ready for flight, and the hard parts in its' Dev Cycle are finished. They'll have plenty of customers, including the U.S. Government if everything goes to plan.

In fact, they have so much commercial work out there to pay the bills, it almost seems like they are the ones helping others right now. As Elon has said in the past, before the onslaught of work...That SpaceX would continue at a slower pace if necessary, but would continue.....Which is why I really hope they put it up on their own shortly and 'buzz" the station with a photo op.....basically tells Boeing .....The new kids are in town, and there not going away!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!