Recommended Posts

October is open to allow pad and transporter-erector mods & preparations for the Dragon V2 pad abort test in November.

OG2 #2 has moved right into 2015 at the request of ORBCOMM. Remember the slip because of a problem with one of their satellites? It required mods, which were also done to the other 5 sats before launch. Now they want to check out those 6 sats on orbit before launching the other 11.

There are a couple other sats that may move into its slot, one for Turkmenistan and one for NASA. Still under discussion.

There has been some confusion about the crs-4 reusability test. It's seems to be clear that the 1st stage is older and didn't have any landing legs. However, some people say that SpaceX may have added landing legs. This would also fit with gwynne shotwells unofficial statement, that there will be no more water landings, rather barge landings and mid term rtls.

Any info or thoughts?

Good arguments both ways but nothing 100% convincing IMO, and SpaceX isn't confirming either way. A very slight tilt towards legs. We'll probably hear after AsiaSat 6 as everyone is pushing to get it up ASAP.

One thing we did hear is that a full-size F9 mockup will be used for the Dragon V2 pad abort test. All the better to accurately simulate such an abort.

SpaceX always said they'd test, use and abuse hardware until they cratered something.

Well, they did it. F9R Dev-1. They probably triggered the flight termination system (FTS.)

No word yet on what they were doing when it happened, but she went out in style.

Rockets are hard?

https://twitter.com/Singer_Matthew/status/502961881280045056

Matthew Singer @Singer_Matthew [spaceX Engineer]:

Yes, there was an anomaly during the #SpaceX F9-R test flight today. No injuries being reported, details of the malfunction to follow

f62814ccbc2432daac8f0d5031f2b0a5.jpg

5fd529522deb1df28bbafa7914173ce6.jpg

http://www.nbcnews.com/news/us-news/spacex-test-flight-explodes-over-texas-town-n186436

A SpaceX prototype rocket automatically detonated after an "anomaly" was detected during a test flight Friday in McGregor, Texas, the company told NBC News Friday night

So it was the FTS that triggered after an anomaly. Did its job.

From one of the tweets it sounded as though the FTS automatically terminated after it detected an anomaly. A rocket that monitors itself and self-destructs when a variable isn't were it should be. That's pretty cool even considering the outcome.

3 engine version? Perhaps a checkout of F9R Dev-2 before being shipped to SpacePort America.

May well have been a bad actuator.

Earlier today, in McGregor, Texas, SpaceX conducted a test flight of a three engine version of the F9R test vehicle (successor to Grasshopper). During the flight, an anomaly was detected in the vehicle and the flight termination system automatically terminated the mission.

Throughout the test and subsequent flight termination, the vehicle remained in the designated flight area. There were no injuries or near injuries. An FAA representative was present at all times.

With research and development projects, detecting vehicle anomalies during the testing is the purpose of the program. Today?s test was particularly complex, pushing the limits of the vehicle further than any previous test. As is our practice, the company will be reviewing the flight record details to learn more about the performance of the vehicle prior to our next test.

SpaceX will provide another update when the flight data has been fully analyzed.

I could turn a bent stick into a weapon (atlatl) and rockets are inherently a bit dangerous so in principle, yes. That's why the US has the ITAR law so its tech can't be openly distributed.

It could have been a loss of an engine steering actuator or some new code had a bug. Time will tell.

So the failure made main stream media. 

 

http://edition.cnn.com/2014/08/23/tech/innovation/rocket-experiment-failure/

 

(I dont usually read CNN it was on the news in my Hotel)

 

But i can tell you it is not a great article, I think the person who wrote it may have ADHD.

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

    • No registered users viewing this page.
  • 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!