Recommended Posts

3 hours ago, DocM said:

FYI, Paragon SDC has won the NASA contract for a new water recovery system on ISS. They developed the Commercial Crew ECLSS used in Starliner and Dragon 2 and have a long history with NASA, Boeing, SpaceX and ISS. 

 

http://www.nasa.gov/press-release/nasa-awards-contract-to-increase-water-recovery-on-space-station

 

http://www.paragonsdc.com/paragon-iwp/

 

 

 

 

 

I went to the "Mars Live Experience" last night and Jason Crusan was talking about this being tested on the ISS for future deployment on Mars. 

SpaceX timeline.

 

FH and F9 development end in about 16 months with Block 5. ITS spaceship testing starts in Q3-Q4 2018.  Booster testing in mid-2019, orbital tests in 2020.

 

From the final ITS presentation pdf.

 

ITS-Timeline-1280.jpg

 

 

  • Like 3

Well, there we have it folks! Red Dragon can start in Feb. 2018, ITS can start flying in August-September 2022. :D That's what I'm lining up the beginning of the lines with. Matches up with launch windows nicely.

probability of next explosion is very high -- Musk et Co must stop gambling on deeply cryogenic propellants ==>> DCP needs the brand new EXPENDABLE rocket. DCP is extremely tricky Beast:

 

1. fuel easily goes 3-stated at once  (it's partially solid, partially liquid & partially gaseous) + fluctuates through that states.

2. material becomes fragile.

3. very limited time to keep fuel stable.

4. chemical surprise (like cool fire) can takeover at any Place, at any Time. 

=====================

Don't gamble with that Beast ==>> There never has mercy. :)

Better tell that to Russia since sub-chilled LOX is required on the Russian engined Antares and Soyuz 2-1v.

 

Sub-chilled LOX at 66°K is liquid, not partially solid (54.6°K) and certainly not partially gas because it's well below its 90.188°K boiling point.

 

Something abnormal in the prop and He loads chilled the LOX enough to solidify it (likely γ-phase) inside the COPV overwrap winding, nowhere else. This has been reproduced, with a loud bang, so preventing it from happening again shouldn't be an issue. 

Edited by DocM
17 hours ago, DocM said:

Better tell that to Russia since sub-chilled LOX is required on the Russian engined Antares and Soyuz 2-1v.

 

Sub-chilled LOX at 66°K is liquid, not partially solid (54.6°K) and certainly not partially gas because it's well below its 90.188°K boiling point.

i think they have followed only well-proven process -- if No, Musk-like stories (Boom, baby, Boom) shall become their fate too.

17 hours ago, DocM said:

certainly not partially gas because it's well below its 90.188°K boiling point.

gaseous state may instantly appear in some locations. solid state in a classical form doesn't exist within the over-chilled medium -- super electrical conductivity + other quantum odds make a material transparent for super cooled Atoms/Molecules.

Quote

SpaceX chief Elon Musk called the problem surprising and said it had never been encountered in the history of rocketry.

But it's not completely unexpected. A panel of highly respected aerospace experts told NASA eight months before the accident that the lack of a re-circulation pump aboard the Falcon rocket could be a safety problem.

RELATED: Dramatic Video Shows Moment of SpaceX Explosion

"We are concerned that there may be insufficient pre-cooling of the tank and plumbing with (SpaceX's) current planned oxidizer fill scenario," former astronaut Thomas Stafford and members of the International Space Station Advisory Committee wrote in a December 2015 letter to NASA.

The letter was released on Friday.

"Without re-circulation there may be stratification of oxidizer temperature that will cause a variation in the input conditions to the oxidizer pump," the letter said.

NASA's space shuttles, for example, used a re-circulation system and pressure lines to help keep liquid oxygen temperatures consistent, Mike Leinbach, former shuttle launch director, told Seeker.

"That's key," said Leinbach.

NASA also has a bit of history with liquid oxygen behaving badly with a composite fuel tank, which was developed as part of the experimental X-33 spaceship in the 1990s.

RELATED: SpaceX Rocket, Israeli Satellite Destroyed

"The composite tank experienced cracks when fueled in development tests. Composite was used to save weight. Never could overcome it technically, and contributed a lot to the program demise," Leinbach wrote in an email.

http://www.seeker.com/spacex-elon-musk-falcon-rocket-explosion-launch-pad-accident-2083614822.html

 

In all fairness we'll call this lesson learned. SpaceX will adapt, and the data gathered on this mishap can be used to prevent occurrences like this one in the future; be it Russia or anyone else. Better that it happen before these rockets have Crews on top of them -- in any Space Program. Don't want any loss of life, injury, or setbacks over something that could have been prevented. (Y) 

 

This is another example of how difficult Space is. 

And LOX stratification in a full tank over time wasn't the issue. The tank was only part full. 

 

As to prop and crew loading...

 

1) you load crew first. The rocket is empty so both the flight crew and ground crew are safe. During fueling the flight crew is buttoned up in a capsule surrounded by thermal protection materials, which is also equipped with a powerful launch escape system looking for an excuse to bug out.

 

It would have easily outrun the AMOS-6 event, as fast an event as one can imagime.

 

2) you fuel first, and expose both the flight crew and ground crew to a rocket filled with 500t of propellants looking for an excuse to go boom. If anything goes wrong both crews are SOL; the launch escape system can't fire and the NASA required zip lines are a joke. Puh-lease. Call the coroner.

 

I'll take door #1.

 

How the NAC avoids common sense sometimes amazes me.

 

 

Edited by DocM
  • Like 1
38 minutes ago, DocM said:

As to prop and crew loading...

much better to use Soyuz-like scheme w/ no DCP as well. other schemes could be adopted to crew vehicle, if they have showed due success rate in cargo flights.

 

46 minutes ago, DocM said:

1) you load crew first. The rocket is empty so both the flight crew and ground crew are safe. During fueling the flight crew is buttoned up in a capsule surrounded by thermal protection materials, which is also equipped with a powerful launch escape system looking for an excuse to bug out.

i've had some doubts about escape system of Dragon ==>> engines of capsule must be as far from 2nd stage as possible, otherwise rocket explosion could affect them.

5 minutes ago, SarK0Y said:

second moment, solid boosters work faster, it's better for escape tower.

Why, when the Dragon 2's propulsion system, at full power, can do the same job at the same response time and speed with less weight? No need for an escape tower that potentially can strike the spacecraft (not to mention add additional weight)?

 

Nah, we like the SuperDraco engines. A lot. :yes: 

  • Like 2
43 minutes ago, Unobscured Vision said:

Why, when the Dragon 2's propulsion system, at full power

perhaps theoretically, practically Musk's "optimizations" have proven self unsafe. i remember how Musk's supporters were blackmailing Shuttle. But in practice Shuttle was more reliable/safe & even more cheap as well.

1 hour ago, SarK0Y said:

much better to use Soyuz-like scheme w/ no DCP as well. other schemes could be adopted to crew vehicle, if they have showed due success rate in cargo flights.

Guess you missed the part about other launchers using chilled LOX. If Shuttle had continued it's quite likely it too would have used sub-chilled propellants, NASA was exploring it and saw no deal breakers, and the required pumps are commercially available. In short, quit the FUD.

 

Quote

 

i've had some doubts about escape system of Dragon ==>> engines of capsule must be as far from 2nd stage as possible, otherwise rocket explosion could affect them.

Dragon 2 pad abort test overlaid on AMOS-6 explosion, timed so the SuperDraco ignition happens after the event started. FYI, the SuperDracos reach 100% throttle in 90-100 milliseconds.

 

 

5 minutes ago, DocM said:

Guess you missed the part about other launchers using chilled LOX. If Shuttle had continued it's quite likely it too would have used sub-chilled propellants, NASA was exploring it and saw no deal breakers, and the required pumps are commercially available. In short, quit the FUD.

Yes, it'd be used WELL-PROVEN PROCESS & RD180-like engines for its boosters :rolleyes:

 

10 minutes ago, DocM said:

the SuperDracos reach 100% throttle in 90-100 milliseconds

your pic just shows how engines of Dragon could be affected by such explosion -- normal escape tower stays safe at any scenario.

Guess you missed the part about RD-180 not being used for govt launches after Vulcan flies. Atlas V then needs to be commercially viable, which it will have a problem doing - too many NON-Russian engined options. 

 

The SuperDraco nozzles are covered by pop-off panels before they fire, and so are protected. After they fire their exhaust velocity is fast and voluminous enough to handle thrusting during a hypersonic re-entry for landing on Mars, so a piddling subsonic fireball is nothing. Try harder.

Just a heads up guys, we can't use the "troll" word without getting a warning.

 

We must agree to disagree and move on with our usual thorough science.

 

You guys are smart and know what to do.

 

Thanks much.    :s

14 minutes ago, DocM said:

I could get very creative quoting that first line DD, but I'll restrain myself.

I'm having one of those days where I feel like a bag of hammers, shouldn't be near a keyboard.....:s

5 hours ago, DocM said:

Guess you missed the part about RD-180 not being used for govt launches after Vulcan flies. Atlas V then needs to be commercially viable, which it will have a problem doing - too many NON-Russian engined options. 

vulcan.png

planned:rofl: i'd like to share you some inside -- this rocket will go nowhere or will have RD yet again :) well, mid-12.16?:)

This topic is now closed to further replies.
  • Posts

    • 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.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!