Recommended Posts

So, it didn't survive the landing, but DID actually make it on target? That's good!

 

Edit: Correction. it DID survive the landing! Even better!


@elonmusk
Didn't get good landing/impact video. Pitch dark and foggy. Will piece it together from telemetry and ... actual pieces.

 

You'd think they'd have multiple redundant camera's going, including night vision ones etc, to handle that.

It was too foggy for good footage, and winds were too probably too high for a dronecam.

Sounds like the grid fins got it to the ASDS just fine, but landing velocity controls need work. They have plenty of opportunities to refine it this year.

Oil leak in the grid fin hydraulics,

@elonmusk

Grid fins worked extremely well from hypersonic velocity to subsonic, but ran out of hydraulic fluid right before landing.

Upcoming flight already has 50% more hydraulic fluid, so should have plenty of margin for landing attempt next month.

Am super proud of my crew for making huge strides towards reusability on this mission. You guys rock!

Something I was thinking about as they did SECO and Dragon Separation (and afterwards). It appears they were watching how the unspent fuel was moving around in the tank in microgravity, and I suspect how much fuel was left over also .. perhaps they are gathering data about what they need to do to recover the second stage? That's the next logical step, and probably it's already "part of the plan".

 

As for having enough fuel to do a controlled return like they want to do with S1, I'm not so sure if that will work here.

 

[EDIT] Cut my own post short. Heh.

 

As I was saying, there are a few ways to recover the Falcon S2. The most economical (but the one with the highest degree of risk) is a free return where the gradual decay of its' orbit combined with some maneuvers could do the job. The return procedure, as I outline below, would still need to be done, but would require less resources. That would take weeks, and I doubt SpaceX would go for that.

 

The other could be increasing the fuel capacity in the S2 in conjunction with using a single or multi-stage Retro-Rocket package to cancel the orbital velocity. The Retros would deal with the orbital velocity, then again to slow the descent rate to prevent damage to the S2 (which is why they would need to be multi-stage). Once down to the altitude where the S1 would be, they could follow the procedure (tweaked for the S2, obviously, due to weight and aerodynamic differences) using the S2's primary engine and a second landing site. And we know SpaceX can do it on one engine because Grasshopper used a single engine for many of it's flights. Apples and Oranges, I know .. ;)

A short gas thruster burp will settle the propellants. No big deal and already done before engine restarts.

My takeaway on this,

1) squash whatever bug is leaking the grid fins hydraulic fluid

2) this was like a night carrier deck landing with a rookie pilot and only 2 wires. They'll get better at it.

  • Like 1

Oh yeah. They've got that figured out already. Very talented group of people over there.

 

The mission isn't even a day old and they're already making improvements for the hardware for the next flight. It's an example of passion, dedication, and outright giving a good golly gosh about what you're doing. :yes:

Well that confirms that they will land on dscovr. Do you really think the hydraulic fluid was leaking? Maybe it wasn't a closed cycle a closed cycle and their tanks were empty. That would make sense since he said they would add 50% more hydraulic fluid.

I still don't see the real benefit of the open-loop system beyond a modest weight savings. And by the time they add the extra fluid for the next mission, they're around the same weight as a closed-loop is, but with a waste/loss factor -- which cuts into the profit margin, however slight. SpaceX needs to watch the books too. ;)

 

Just go with a closed loop system, build in some redundancy to cover failure scenarios, tweak accordingly, and test it for worthiness then get the flight cert. It's slightly heavier, but far more reliable, and it will save money in the long run.

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

    • No registered users viewing this page.
  • Posts

    • Doesn’t surprise me at all. God is light & He gave us life so it sounds almost logical that we would therefore emit a certain amount of light.
    • This is what I want. Hey Gemini, how do I remove you from all my google products permanently?
    • I would never install install this build before rtm process. only 3 months to go. never install on your daily devices. just wait 3 months.
    • Motrix Next 3.9.6 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.6 changelog: New Features Clipboard management — App-owned copy actions no longer trigger the Add Task auto-detect popup. aria2 input compatibility — Multi-line aria2-style task input is supported for URLs with per-task options such as out=. BitTorrent IPv6 DHT — Added IPv6 DHT support and related configuration. File category URL patterns — File category rules can match URL patterns with validation and localized hints. Task status tags — Added clearer waiting and sharing states for task cards. Download event bridge — Added an aria2 WebSocket event bridge for faster download notifications. Improvements Improved task list transitions and preserved task state during tab switches. Kept RPC origin access enabled for local integrations. Restored AppImage stripping in release builds after beta validation. Added localized preference guidance across supported languages. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Segra 1.6.2 by Razvan Serea Segra is a free, open-source OBS-powered game recorder offering fast gameplay capture, instant clips, AI highlights, deep game integration, and seamless uploads—perfect for gamers, streamers, and content creators. Lightweight, fast, zero bloat. Segra key features: Automatic Game Recording: Begin capturing gameplay the moment your game launches, with zero manual setup. Instant Clipping: Save important moments instantly using a customizable hotkey—perfect for highlights, montages, or quick shares. Segra AI Highlights: Let Segra automatically detect kills, assists, deaths, and key events to generate polished highlight reels without manual editing. Gameplay Uploads: Upload recordings and clips directly to Segra.tv for fast sharing and cloud access. Deep Game Integration: Enjoy advanced game-data tracking across hundreds of supported titles, enabling smart highlight generation and stat-informed clipping. High-Performance Capture: Record up to 4K at 144 FPS using OBS-powered technology with minimal performance impact, supporting NVENC, AMD VCE, and custom quality controls. Segra Editor: Edit recordings easily with timeline controls, segment management, and event-based navigation to build the perfect clip. Customization Options: Adjust hotkeys, output formats, storage paths, codecs, capture quality, and performance settings for a tailored recording experience. Segra 1.6.2 changelog: UI: Improved the transition from the loading skeleton to the real content card. Security: Added Segra.dll code signing and automatic VirusTotal upload. Settings: Fixed the settings header to highlight Account when scrolled to the top. Recording: Updated OBSKit.NET to 1.4.1. Download: Segra 1.6.2 | 74.5 MB (Open Source) View: Segra Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Conversation Starter
      sumytbe earned a badge
      Conversation Starter
    • One Year In
      B4dM1k3 earned a badge
      One Year In
    • One Year In
      DarkWun earned a badge
      One Year In
    • Dedicated
      Almohandis earned a badge
      Dedicated
    • Dedicated
      JuvenileDelinquent earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      181
    3. 3
      PsYcHoKiLLa
      86
    4. 4
      Michael Scrip
      78
    5. 5
      Steven P.
      75
  • Tell a friend

    Love Neowin? Tell a friend!