Iron Hill Project Thread

Good news: Chronus is in orbit, aligned with Discovery and with about 7 km/s of delta-v, despite the wacky ascent I made. LaunchMFD heading AP had an unexpected behaviour and I got distracted a little bit.

Bad news: ETA is at 15:30 UTC Nov 22. Discovery was about 180 degrees from the launch site at launch time (but well aligned), so we'll have a Soyuz-like sync profile.

ETA can be moved only foward (I can't low the perigee).

As I can't be at home before 17:00 UTC, I'll move ETA to thursday evening (between 20 and 24 UTC). Is there any problem for the crew with this schedule?
 

Attachments

I'm having connection problems, AGAIN! :beathead: :compbash:
But sorindafabico updated the clock yesterday, so I don't need to post it again...

Good luck in your mission, sorindafabico! :thumbup:
 
Is there any problem for the crew with this schedule?
I'm free then--but we can station-keep for a day or two if we have to (though I'd rather not take the consequent chance of screwing up the clock if we can avoid it).

Did you happen to get a recording of the launch? Also, who did you take along for to man Discovery?
 
After Discovery TLI.

---------- Post added at 07:05 AM ---------- Previous post was at 05:48 AM ----------

New ETA: today, 23:20 UTC.
 
Ready to TLI TMac :salute:

---------- Post added at 06:44 PM ---------- Previous post was at 05:24 PM ----------

Having some issues on the last state (random CTDs). We are on Quakenet.
 
Discovery is now under a 48-hour hold due to a computer malfunction. New launch date is November 25, 19:45 UTC. Crew will be:
Pilot: Rtyh-12
Commander/Navigator: SolarLiner

Sorry about this, guys. We're doing everything we can:(

---------- Post added at 03:08 PM ---------- Previous post was at 02:41 PM ----------

Discovery, we're now reading your malfunction (it's happening on my computer now, so it can't be an add-on problem...).

We're working on the problem...
 
What exactly does this mean? Are we meeting then or do we keep the date you sent the PM about?
 
We will meet at 19:45 UTC on the 25th:yes:

Discovery, I believe we've found a solution. Under the updater, there are two drop-down boxes. Make sure the top one is set to "Propagate along osculating elements" and the bottom one is set to "Maintain surface position". That should fix it:)

NOTE: Even if this works, the 2-day hold will remain in effect, to avoid confusion.
 
Last edited:
Alright, the mission is on hold for another 24 hours. Next attempt will be at 20:40 UTC November 26.

I need all B-Crew members to list what operating system they are using.

Windows XP here, although I sometimes use Quakenet from my Linux box:)
 
Good old Win95 :rofl:
Seriously, I'm on a Windows 7 machine. For the problem I see only the SAS module (the DLL) causing the problem because the other add-ons are UCGO, UMmu, or Spacecraft3 files. I'll try without it, as quick as I can.
 
Back
Top