Recommended Posts

Looks like it's stackable, too. FH could likely carry as many as will fit inside that huge fairing ... all it needs is a heavier interstage mount to hold the weight of all those birds and the dispensers onto the S2, and presto. Happy customer. :yes: 

  • Like 1

Confirmed: the first reflown Falcon 9 will use the CRS-8 core. They're finalizing an agreement with the customer.

 

Also, SpaceX believes they've found a way to better protect the engines during reentry, this so that fluids do not boil and the engines restart normally. Sounds like another protruding nail has been countersunk.

Edited by DocM
  • Like 1

More on the new SpaceX satellite dispenser. With the 2 tiers shown it masses 1 tonne.

 

Looks like the tiers are generic; stack more for increased capacity.  Time for a longer fairing :)

 

Quote

SpaceX developed a Falcon 9 satellite dispenser unit that was capable of managing the critical-timed separation and deployment of ten satellites from each rocket. These dispensers were built out of a carbon fiber composite to reduce mass, minimize the total number of parts and simplify their composition while increasing structural stiffness and strength. The design of this dispenser places the Iridium NEXT satellite vehicles in two separate stacked tiers around the outside of each dispenser, holding five satellites per tier.

 

spacex iridium dispenser-web.jpg

  • Like 2

Yessir. Now we're talkin'. Looks like they're gonna need longer fairings. :yes: Plus, if they're built smartly, they can get a longer fairing out of (roughly) the same weight or even less as the current ones using Carbon Fiber for the shell and wider crosshatches to add rigidity .. yeah.

  • Like 1

Now that SpaceX has CRS-9 launched, and the S1 has landed at LZ-1 in magnificent shape, and interesting idea comes to mind about what SpaceX can do next to really challenge themselves before the Falcon Heavy and Dragon 2 Test Programmes get underway in 4Q 2016+.

 

Since the ultimate goal of reuse is "rapid turnaround", I propose that SpaceX starts putting some more of it into actual practice. Bear in mind that I'm gonna walk the process backwards. 

 

We already know that they've made huge headway in the Falcon 9 loading/unloading procedures regarding preflight and fuel/LOX -- they can do all of the preflight stuff in about 35 minutes, with going vertical in about 9 minutes and an hour to connect Fuel Lines, other Launch Hardware and go through checklists (I assume).

 

Takes them, what, an hour to rollout to the Pad from the Hangar/Integration Building? Two, even?

 

In the H/IB, it takes Marty and the Wonder Workers a full day to get a payload strapped onto an S2 & an Interstage and Fairings secured for Flight, maybe two. Of course, they can have this work done before it actually needs to be mounted to an S1. Preparation work is going to be everything with rapid turnaround, so yeah, they'll wanna have S2's on upward done ahead of time.

 

So let's say that Marty and the Wonder Workers have done this work ahead of time, and that the S1 is already on the Launch Pad and they haul the S2 on upwards out to the Pad and perform the integration there. It's a timesaving measure, but it'll still take them three hours to get it mounted and connected up. Afterwards, the Strongback will erect the now-complete Falcon-9 and the Preflight stuff can start once everyone has cleared out. Hell, they could even be waiting for the S1 to arrive from the Hangar after the below paragraph, saving some time. :yes: 

 

All that's missing, now, is how our S1 got there. We've landed at LZ-1, obviously. The S1 is in great shape, no issues. The Recovery Crews have quickly and expertly done their stuff, and the recently-landed S1 has been re-certified for flight, cleaned up, hauled back to the Hangar and lifted back onto a Strongback for the next launch. I'm suggesting that this process, total, will take six hours.

 

So, by my chunkulation, SpaceX could theoretically perform a Reflight on the same S1 with another payload within 12 hours. :) I'm sure they'd like to get that number lower, but I don't see that number being realistically lower than eight.

 

Your thoughts, anyone?

Assembly of any complicated nature is generally not done in the open due to environmental conditions for the workers and equipment, FOD, security concerns and company proprietary secrets.

 

Systems checks will also require test equipment, some of which are probably not portable.

 

:)

  • Like 1
1 hour ago, DocM said:

More likely they use a queue with weeks between each cores flights.

 

24 minutes ago, Draggendrop said:

Assembly of any complicated nature is generally not done in the open due to environmental conditions for the workers and equipment, FOD, security concerns and company proprietary secrets.

 

Systems checks will also require test equipment, some of which are probably not portable.

 

:)

Valid points. I was thinking of my example more in an experimental & testing scenario. A "let's see if we can actually do it" sort of thing. :) 

  • Like 1

Draft EIS for SpaceX's Vandenberg SLC-4W stage landing complex.

 

It gives some propellant load info for F9 FT, and it reveals the grid fins give the first stage a cross-range of 25-50 km. 

 

Very interesting, if longish, read.

 

http://www.nmfs.noaa.gov/pr/permits/incidental/research/spacex_2016iha_draftea.pdf

  • Like 2

Thank's...just downloaded the pdf. Should have some buried goodies.

 

The S1 does present a large cross section for "lifting body" use, and by the looks of it, SpaceX uses it to advantage...nice...:)

  • Like 1
On 19/07/2016 at 11:44 AM, jjkusaf said:

Found this video interesting.  

 

<snip>

Thanks for sharing this, I always find these topics pretty interesting but way over my head so it was nice to have a much simpler view on what SpaceX are doing.

  • Like 3

Slow Sunday for news, so I thought that I would "space spam" the thread with some SpaceX art themes from Stanley Von Medvey, which you have probably seen before, but look more relevant every day that passes...

 

Image sources

 

SHLV_Return.jpg?1414884749

credit Stanley Von Medvey

 

 

 

Shipping_Center_cgtalk.jpg?1414887041

credit Stanley Von Medvey
 

 

 

o4hLw.jpg

credit Stanley Von Medvey
 

:)

  • Like 2
This topic is now closed to further replies.
  • 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!