>>
|
2b3ecb.jpg
Lucky Posh
2b3ecb
Yes, of course, why didn’t you think of that? You shake your head. Your headache is one of those constant dull ones, and it’s getting worse.
You get out the spool of spare wire, run some new wires and get out the backup hard drive. The circuit check between the monitors in the cockpit, the drive, and the new “server” checks out, so you hook up the infirmary computer to the backup drive. You don’t check or connect any of the other wires that connected the old server to the rest of the ship just yet – one thing at a time, you’re thinking.
It loads for a little while, and then eventually starts up – though you leave the backup computers running vital systems disconnected for now. The logs are lost, unfortunately, but it seems you may have a viable replacement server… as soon as you test and hook up all the other circuits.
Strapping back into the pilot’s seat, you get ready to sift through the nav data and look at your options, when a double-take becomes necessary: the magnet cooling time is now “–”. A re-scan only brings back the “MAGNET NOT DETECTED” errors, which don’t go away this time.
The procedure manual recommends visual inspection, and suggests that if the magnets appear undamaged, the control chips may have failed. The recommended course of action is a manual bypass of the affected magnet, as there are several emergency magnets the reactor computer can use to compensate. It does not, of course, have a recommended course of action for when ALL the magnets are not detected.
>>manual control for the reactor
There isn’t really. The current reactor design allows it to run for as long as several seconds before magnetohydrodynamic instabilities will cause the plasma current to quench, but without micro-adjustments, sustained fusion won’t be possible and the reactor will vent the reaction mass to space (and hopefully avoid destroying itself) when it quenches. Unfortunately, if all the magnets’ control chips were damaged, the sensors needed for the computers to make adjustments probably won’t work either….
You analyze your options, assuming for the moment that the MPDT’s delta-V is unavailable to you. There IS a manual control for the engines, but you shouldn’t need it because the backup GN&C also has control.
Planet 2 is ahead of you, but without some circularizing and some phasing, it will take several orbits before you’re captured. You might have enough fuel to end up in orbit sooner, but without a lander, there’s not much point. Even if you sprayed a perfectly-distributed coat of heat shield on the correct parts of the ship, there are no atmospheric control surfaces or parachutes to help you land.
Planet 3 is behind you, and circularizing in a higher orbit so it can catch up to you will probably take most of your fuel and about 16 hours. Going around is a definite no, because Planet 3’s year is roughly 390 days long, as your mission clock measures days, and the fuel cells won’t last that long – which means your CO2 scrubbers won’t, either.
A search for workable sundivers proves fruitless, the fact that the emergency engine draws on the same fuel cells as everything else proving to be too limiting… not to mention that you’re not sure the Voyager has sufficient shielding to actually survive the maneuver.
You almost do another double-take. Has object ‘b’ changed orbits? More out of curiosity than anything else, you punch it into the computer as a potential destination. It comes back with sort-of-good, sort-of-bad news: if you burned most of your fuel, you could cross orbits with object ‘b’ within 8 hours.
|