Recommended Posts

Yup, the same booster (B1061) for Crew-1 and Crew-2. Whodathunk NASA would do this a few years ago?

 

Date: April 22, 2021

Time: 0611 Eastern (10:11 UT)

Pad: LC-39A

Booster: B1061.2 (Crew-1)

Booster recovery: yes

Spacecraft: C206.2 Endeavour (DM-1)

 

Crew

 

Commander: Shane Kimbrough (NASA)

Pilot: K. Megan McArthur (NASA)

Mission Specialist 1: Akihiko Hoshide (JAXA)

Mission Specialist 2: Thomas Pesquet (ESA)

 

IMG_20210401_192943.jpg.c831dfd1aae8d6a709c0d114ee703f28.jpg

IMG_20210401_192939.jpg.0237629de8938e827baaab1551616afb.jpg

 

Link to comment
https://www.neowin.net/forum/topic/1406613-crew-dragon-crew-2-mission/
Share on other sites

  • 2 weeks later...
8 hours ago, Skiver said:

So both the Falcon 9 and the Dragon module have flown before? 

I did not expect Nasa to be so on board with this so quickly, man that's so awesome. 

 

NASA has been allowing reused Cargo Dragon and F9's for CRS missions for some time. That experience, plus seeing up close how good the DM-1 and DM-2 vehicles & F9's looked after 1st use, brought on the policy change for Commercial Crew.  

 

Telling is Kathy Leuders* management score for SpaceX in the Starship HLS Source Selection Statement. Minds have changed in the upper floor offices of NASA.

 

Blue Origin's team included Lockheed Martin, Northrop Grumman and Draper Labs.

 

* NASA Associate Administrator of the Human Exploration and Operations (HEO) Mission Directorate

 

20210417_020804.thumb.jpg.447e82c5a86ac00fccd00390a21e7de1.jpg

15 hours ago, DocM said:

 

NASA has been allowing reused Cargo Dragon and F9's for CRS missions for some time. That experience, plus seeing up close how good the DM-1 and DM-2 vehicles & F9's looked after 1st use, brought on the policy change for Commercial Crew.  

 

Telling is Kathy Leuders* management score for SpaceX in the Starship HLS Source Selection Statement. Minds have changed in the upper floor offices of NASA.

 

Blue Origin's team included Lockheed Martin, Northrop Grumman and Draper Labs.

 

* NASA Associate Administrator of the Human Exploration and Operations (HEO) Mission Directorate

 

<snip>

That's a good point actually, I didn't consider the use of Dragon in the CRS missions as any form of evidence in terms of reuse. 

Yep, it was hard to believe the before and after in the picture you posted were of the same dragon module, we've all seen the slightly sooty Falcon 9s when they've been re-used. I know it doesn't make so much sense to get those back to pristine condition but I can understand why they probably spent a bit more time on Dragon to make it look brand new.

 

It's hard to imagine things going much quicker but I wonder if winning this bid will speed up anything with regards to starship development. Whether that's somehow throwing a bit more money at the building of Starship/Super Heavy or more work happening at the overall site build in Boca Chica.

3 hours ago, Skiver said:

That's a good point actually, I didn't consider the use of Dragon in the CRS missions as any form of evidence in terms of reuse. 

 

It goes beyond Dragon. Both NASA and DoD contracted with SpaceX to get "special insight" into their construction and refurbishment processes, and how they evolve vehicles based on refurbishment data. Both liked what they saw, a lot.

 

Quote

Yep, it was hard to believe the before and after in the picture you posted were of the same dragon module, we've all seen the slightly sooty Falcon 9s when they've been re-used. I know it doesn't make so much sense to get those back to pristine condition but I can understand why they probably spent a bit more time on Dragon to make it look brand new.

 

Not that much time. Dragons are skinned using screwed-on cast panels made of SPAM; SpaceX Propriatory Ablative Material, a very inexpensive heat shield "wallboard" SpaceX developed.

 

In most cases removal, inspection, and a Scotch Brite scrub and re-coating with a SPAM based "whitewash" is enough.  If there's too much damage to a panel they just replace it and re-spray the livery. They use a SPAM putty to cover the screw heads.

 

Quote

It's hard to imagine things going much quicker but I wonder if winning this bid will speed up anything with regards to starship development. Whether that's somehow throwing a bit more money at the building of Starship/Super Heavy or more work happening at the overall site build in Boca Chica.

 

Yes, it'll speed things up. Starship will very likely use adapted versions of the Crew Dragon hard and soft-ware - no need to totally  reinvent the wheel. Chromium based multi-screen UI, etc. 

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

    • Turbo Pascal was my first real programming experience more than 30 years ago at university. I mostly taught myself from the included examples and help documentation, because the university only taught the basic syntax and philosophy of Pascal, without going deeply into Turbo Pascal’s advanced features. I still remember when I discovered that I could embed assembly language directly into Pascal code, call BIOS functions, manipulate screen memory, use mouse interrupts, and control peripherals from my programs. That opened huge doors for me. Programming back then felt really fun, direct, and close to the machine. What I loved about Pascal was its readability and the almost instant compile time. Turbo Pascal was an amazing environment, but unfortunately Turbo Pascal for Windows 3 did not feel like it fully carried that legacy forward. Later, Delphi got things back on the right track after the messy transition to TP for Windows. Sadly, Delphi suffered from years of uncertainty as it moved from Borland to CodeGear and then to Embarcadero. That instability made many developers lose confidence in it, even though Delphi itself remained a powerful and productive tool. I still work with Delphi from time to time, but I definitely miss the old days of Turbo Pascal.
    • I hope this encodes in to AV1 or AV2 as currently tiktok uses h265 and h264.
    • Qualcomm reportedly in talks to build custom video chips for TikTok parent ByteDance by Karthik Mudaliar Qualcomm is reportedly in advanced discussions to provide custom chip-design services to Chinese tech giant ByteDance, the same company behind TikTok. According to a report from Reuters, Qualcomm could be involved in designing custom silicon tailored for ByteDance's massive data-center workloads. If it goes through, the deal would make ByteDance one of Qualcomm's early anchor customers for its fastly growing custom chip-design division, For years, Qualcomm was the king of making smartphone processors and modems. The company has also been moving into the PC ecosystem and other formats such as on-device AI for Android XR headsets. However, this particular deal is about Qualcomm's custom Application-Specific Integrated Circuits (ASICs). For a platform like TikTok, ByteDance needs hardware that can help it ingest, process, and serve billions of short-form videos daily. Generalised hardware is no longer the most cost-effective and efficient route, which is why ByteDance is trying to develop custom Video Processing Units (VPUs). VPUs designed specifically for ByteDance’s algorithmic needs could drastically reduce data-center power consumption and improve encoding speeds at an unprecedented scale. The underlying tech behind these processors is actually from Qualcomm's recent acquisition of AlphaWave Semi, a high-speed connectivity specialist company. By combining AlphaWave’s high-bandwidth IP with Qualcomm’s architectural expertise, the company could begin mass production by the end of 2026, if the talks go through. All this also comes at a time when U.S.-China tech relations have dwindled. Escalating trade frictions between Washington and Beijing have severely impacted the export of high-end AI chips from U.S. firms like Nvidia, AMD, and Lam Research. Yet, the Qualcomm-ByteDance discussions show that U.S. tech companies are still actively seeking growth avenues and are open to doing business with China, where regulators still permit. Reuters notes that the outcome of this deal could be uncertain, and ByteDance might also seek partners other than Qualcomm. via Reuters | Image via DepositPhotos.com
  • Recent Achievements

    • First Post
      Almohandis earned a badge
      First Post
    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      456
    2. 2
      +Edouard
      164
    3. 3
      PsYcHoKiLLa
      117
    4. 4
      Michael Scrip
      83
    5. 5
      Xenon
      69
  • Tell a friend

    Love Neowin? Tell a friend!