Recommended Posts

1 minute ago, DocM said:

Since a joint SpaceX-NASA fix for the microcracking is said to be on the Block 5 vehicle, and only new cores will be used for astronaut rides, I doubt they'll need to be concerned.

True, and quite frankly, they don't need to be concerned with the block 3's. This sideshow has just forced NASA to "cover themselves just in case", which they are properly obliged to do.

 

:)

  • Like 1

Agree with all on this. Block-5 Falcon 9's are the ones being used for Crewed Dragon 2's, so there's going to only be "buckle up"'s and "yeehaa"'s all the way uphill. :yes:

 

And then SpaceX can focus on BFR/BFS (whatever they end up changing the name to -- because "ITS" isn't a very good name, per Elon, and they want to change it).

  • Like 1
11 minutes ago, Unobscured Vision said:

Agree with all on this. Block-5 Falcon 9's are the ones being used for Crewed Dragon 2's, so there's going to only be "buckle up"'s and "yeehaa"'s all the way uphill. :yes:

 

And then SpaceX can focus on BFR/BFS (whatever they end up changing the name to -- because "ITS" isn't a very good name, per Elon, and they want to change it).

I kind of like ITS for acronyms...It's The Show!....Incredible Tall Spaceship...It's The Solution....If Terrified,Scream....:woot:

  • Like 1

A lot has happened since the last time I was on here. 

DocM could you give us any hints on how far away this big news is that you are teasing? 

Not sure if this has been discussed before, but do we have any idea what they learned from inspecting the landed cores, if they had any challenges refurbishing them or test firing them? Also with Block 5, what does easier to reuse mean?

16 hours ago, Draggendrop said:

Very bad manners....insert +John avatar shaking finger at them....bad...bad bad bad...:woot:

Couldn't agree more!

 

I've heard SpaceX has finished the prelims for their spacesuit testing. Did I dream that or was it actually reported? Also, I assume it'll be an IVA? 

 

I'm thinking it'll be a bit like: 

tron.jpg

  • Like 3
8 hours ago, PaulRocket said:

A lot has happened since the last time I was on here. 

DocM could you give us any hints on how far away this big news is that you are teasing? 

Can't. Maybe soon.

 

Quote

Not sure if this has been discussed before, but do we have any idea what they learned from inspecting the landed cores, if they had any challenges refurbishing them or test firing them? Also with Block 5, what does easier to reuse mean?

We've learned the JCSAT-14 core has endured no less than 8 successful unrefurbished (but cleaned) burns on the test stand, with a mass simulator the mass of an upper stage and satellite on top,  which says a helluva lot about Block 3. They'll probably keep putting it up until it fails.

 

Block 5 has a ton of upgrades including new landing legs, many reusability upgrades, helium system and COPV changes, yet another thrust boost (!), and even before Block 5 a test of recoverable fairing halves.

 

That's right kiddies, fairing halves which have a reaction control system and parafoils which can fly them to a sea landing for retrieval and reuse. 

 

Landed JCSAT 14 state test a few months ago. The T shaped yellow object with guy wires is the mass simulator. It just keeps on tickin'. It was tested again last month.

 

 

Edited by DocM
  • Like 2
21 hours ago, DocM said:

Can't. Maybe soon.

 

We've learned the JCSAT-14 core has endured no less than 8 successful unrefurbished (but cleaned) burns on the test stand, with a mass simulator the mass of an upper stage and satellite on top,  which says a helluva lot about Block 3. They'll probably keep putting it up until it fails.

 

Block 5 has a ton of upgrades including new landing legs, many reusability upgrades, helium system and COPV changes, yet another thrust boost (!), and even before Block 5 a test of recoverable fairing halves.

 

That's right kiddies, fairing halves which have a reaction control system and parafoils which can fly them to a sea landing for retrieval and reuse. 

 

Landed JCSAT 14 state test a few months ago. The T shaped yellow object with guy wires is the mass simulator. It just keeps on tickin'. It was tested again last month.

 

 

Interesting, definitely excited about the news without knowing what its about. 

Does cleaned mean just the engines? Would love to see what these babies look like when their cleaned. 

 

What are reusability upgrades? Things like easier swap ability of components like the engines and the cork heat shield? 

Really looking forward to the first reflight with SES-10.

  • Like 1

AFIK they've been cleaning off the engines and the inside of the Octaweb (engine bay/mount.) Likely replace eroded thermal protections. The core itself stays dirty.

 

Reusability upgrades include upgrading the thermal protection coatings in and outside of the engine bays - like replacing the cork with something tougher, replacing the thermal shield blankets around the upper nozzles with something more durable, further hardening of the helium system and COPV's, replacing the turbine design to eliminate microcracks,  .. a general toughening up.

 

Engines before cleaning. The white deposits are a residue from the TEA-TEB ignition fluids used to restart the boostback, re-ntry & landing engines (center, 6 and 12 o'clock.) You see it more on the external ring engines as the center engine burns longer and cooks the deposits off.

 

24175842635_c0d63a05bb_k.jpg

 

 

 

 

  • Like 2

 

 

From the last batch, 5 in higher orbit, 1 in transfer, 4 in original placement. Every 2 to 3 days, one is being moved up. Still in the process between Iridium and it's insurer. Once the insurer is happy with functionality...away we go.

 

:)

  • Like 1
6 minutes ago, Unobscured Vision said:

They seem happy with their delivery. :yes: 

When the insurers are happy after this, and the next launch placement in approx April, they may go to 45 days between launches....hope so.

  • Like 1

Vandenberg still has to get their autonomous flight termination gear programmed now that Falcon 9 uses it. Should be wrapping up.

 

The base has been working on a major redoing since last summer; moved their buildings, new hardware and infrastructure etc. to support commercial operators. 

  • Like 1

I'm not so sure about automating the approval process though. Should still be humans in the loop -- sometimes there will be logistics going on that a department will be able to handle better than automation. For example, equipment arriving in the port that will cross through the no-go zones, or even visiting military vessels that are passing through. Don't need an incident.

 

Although I do agree that the approval process needs retooling and a serious overhaul to eliminate the bureaucracy (and thus save time), I think it could (and should) still have people there. :) 

On ‎2‎/‎5‎/‎2017 at 4:53 PM, DocM said:

Landed JCSAT 14 state test a few months ago. The T shaped yellow object with guy wires is the mass simulator. It just keeps on tickin'. It was tested again last month.

What's the point of the mass simulator if it's being held down?

2 minutes ago, DocM said:

To simulate the mass loads on the first stage and interstage during a launch; upper stage, payload, fairing etc. 

Sorry.  I'm not sure I understand yet.

 

You put a car up on jacks and hit the gas, it's not going anywhere no matter how much mass is in the vehicle.  I'm just comparing that to a rocket that you clamp down, it's not going any where.  I don't understand why the mass loads matter (unless it's for vibrations or something like that).  I know a car and a rocket are very different, just an easy way to ask my question I think.

It's also to help weigh the rocket down. Those guide wires, by themselves, and the clamps used at the bottom of the stage, are quite stressed during static firings and the mass simulators allow SpaceX to crank up the throttle without the rocket getting away from them. It's for safety, first and foremost.

  • Like 1

The vertical and vibratory loads of an integrated rocket vehicle vs those of a bare lower stage are very different from a car racing it's engine on blocks.

 

In addition to safety, Falcon 9 doesn't use a separate chassis with tanks inside, it's a monocoque - the stressed skin IS the tank and the loads on top cause it to behave differently during the burn. There are accelerometers all over that stage measuring every vibration, deformation etc. looking for a variance outside of the allowed ranges.

  • Like 2
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!