Recommended Posts

2 hours ago, Skiver said:

Has their been any offiicial feedback on if/how successful the test was? I assume a true official post on this might be days away?

yea, I'm not sure of any more "scheduled" updates regarding the test aside from the post-launch briefing held yesterday.  During that briefing Elon said crewed flight will likely take place in the second quarter of this year.  I would assume if everything went as expected during the test then crew will be going up in Apr-Jun.

 

 

Thought this video was pretty neat ...

 

 

That thing looked like it dropped quite a bit before the chutes filled up fully with air, and the capsule was very violent, 30-~50sec mark in the post 1 video flipping on its head and back, until the chutes started to get air in them.  That doesn't look very good for the passengers.    

14 minutes ago, sc302 said:

That thing looked like it dropped quite a bit before the chutes filled up fully with air, and the capsule was very violent, 30-~50sec mark in the post 1 video flipping on its head and back, until the chutes started to get air in them.  That doesn't look very good for the passengers.    

It had two "passengers" all wired up so they'll know how much force was exerted on "them".  Obviously it is more about survivability than comfort.  

  • Like 1

They purposely induce a slow opening of the chutes to minimize forces exerted on the chutes and capsule.  The speed and duration of the free fall won't harm anything, but the forces during decel can.  Slow and controlled is key.

45 minutes ago, Jim K said:

It had two "passengers" all wired up so they'll know how much force was exerted on "them".  Obviously it is more about survivability than comfort.  

And I kind of question the survival of the occupant returning to normal quality of life or being incapacitated on some front by being jostled around like that.  Just because your head has padding, doesn't mean your brain does.  Brain getting slammed against your own skull isn't exactly good and why concussions are taken very seriously.  Could this lead to more than a concussion?  It would be interesting to see the data or explanation of the abrupt tilting/jostling to know that it is within "normal" limits.  Hard to tell gforces from here.

7 minutes ago, sc302 said:

And I kind of question the survival of the occupant returning to normal quality of life or being incapacitated on some front by being jostled around like that.  Just because your head has padding, doesn't mean your brain does.  Brain getting slammed against your own skull isn't exactly good and why concussions are taken very seriously.  Could this lead to more than a concussion?  It would be interesting to see the data or explanation of the abrupt tilting/jostling to know that it is within "normal" limits.  Hard to tell gforces from here.

Yea...the data will provide the answers. Forgot the astronauts name...Hague I think...described the Soyuz abort (in '18) like a roller coaster and being tossed around. I personally (as a certified armchair astronaut) didn't really see anything unusual/alarming.

11 minutes ago, Jim K said:

Yea...the data will provide the answers. Forgot the astronauts name...Hague I think...described the Soyuz abort (in '18) like a roller coaster and being tossed around. I personally (as a certified armchair astronaut) didn't really see anything unusual/alarming.

@sc302is referring to the video Doc posted in the OP. That was the pad abort test from 2015. That test is indeed a far more violent experience and would be quite uncomfortable for the occupants, especially since there would be little to no warning that it was going to happen. The large amount of thrashing the capsule does is due to that fact that it is still very much in the atmosphere and can't use its thrusters to stabilize. The idea here though is living is better than not living when trying to escape an explosion on the pad.

 

The In-Flight abort test from Sunday is a much smoother experience. The occupants are already experiencing a lot of acceleration so when the escape system activates it is just a bit more in the same direction. They will certainly feel it but will already be braced since they were already in flight. Some data was reveled at the press conference showing forces never exceeded 3.5g throughout the test with the NASA director even commenting that it was "impressive" to achieve that low of a number in a launch escape. The Soyuz capsule will reach over 6g during its escape which saved two lives in 2018 as Jim points out.

  • Like 2
5 minutes ago, rdlenk said:

@sc302is referring to the video Doc posted in the OP. That was the pad abort test from 2015. That test is indeed a far more violent experience and would be quite uncomfortable for the occupants, especially since there would be little to no warning that it was going to happen. The large amount of thrashing the capsule does is due to that fact that it is still very much in the atmosphere and can't use its thrusters to stabilize. The idea here though is living is better than not living when trying to escape an explosion on the pad.

 

The In-Flight abort test from Sunday is a much smoother experience. The occupants are already experiencing a lot of acceleration so when the escape system activates it is just a bit more in the same direction. They will certainly feel it but will already be braced since they were already in flight. Some data was reveled at the press conference showing forces never exceeded 3.5g throughout the test with the NASA director even commenting that it was "impressive" to achieve that low of a number in a launch escape. The Soyuz capsule will reach over 6g during its escape which saved two lives in 2018 as Jim points out.

aaaah.  Yea, that one did look a little rough.  :)

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!