The count is back on (if you can believe the blog–he says not to, probably to cover his keister). If there were no problems, the test should have occurred by now.
[Update at 4:05 PM EST]
Close, but no cigar:
A few seconds before the engine ingited [sic], the count was held.
They are now safing the vehicle and we will find out soon if they will restart the count and take it all the way to ignition.
It’s sounding like a good thing that they did this test before launch. I think they’re finding out how hard building and flying rockets is.
[Update about 4:30 PM EST]
They’ve recycled the count to T-15 minutes.
I find the fact that they can take the engine all the way to ignition and recycle to a fifteen-minute count a testament to the simplicity of the system (none of this having to empty tanks and recycle to the next day stuff). I’m not sure what it says about reliability at this point, though.
[Update at 4:50 PM EST]
They’ve stopped the count again, but this latest post expands on my comments above about repeated launch cycles, and how far the technology has allowed us to come in that regard. It also provides some explanation of the issues they’ve been encountering today.
Once again, though, it points out that they weren’t ready for prime time when it came to launching (and that these test firing rehearsals were a good idea). That’s what test flights are for, and so far, while they haven’t launched, they haven’t lost anything, either, except some time. Hopefully, this “shakedown cruise” will reveal a lot of things that will give them better schedule reliability in the future.
[Another update a couple minutes later]
It really is a family affair. Note the last name of the commenter to this latest post.
[Update a few minutes later, for those not following the Kwajrocket blog]
They’ve emptied the propellant tanks and are analyzing data, but it doesn’t sound like they’ve yet given up on an engine firing today.
[Late night update]
Two to four weeks (sorry, no permalink–just click on the link to “New Launch Date Update.”)