nanosat programming questions
Posted: Thu Jul 03, 2014 9:39 pm
I'm pretty ignorant of what today's hardware and software is capable of and even what are the right questions to ask here. So I'll just stumble along and hope someone will be kind and fix the questions themselves.
Lets suppose you have a working, low thrust Mach-Effect Thruster that will fit into a cubesat, and you want to fly it around in deep space as part of a TRL7 demonstration of the technology. So you want to build a cubesat. And lets get crazy (because it's fun) and say that you have a radiation hardening technique you want to try out too, and if it works, you can fly through the Van Allen Belt unscathed. Since MET's don't run out of propellant, once you're clear of the VAB, you can go anywhere you'd like. You can for instance go cislunar. Cislunar is good. It's close enough to mother Earth that you can likely stay in touch and confirm the status of your spacecraft.
So that's 3 stages of mission. First to fly to equatorial orbit. Second to fly through the VAB. Third to fly to the Moon. And lets get all crazy and say forth you wrap around the moon, and fly off to Mars while its opposed to Earth. You cut across the system where there's lots of sunlight and say hello to NASA's first gen Elektra radio aboard the Mars Recon Orbiter as you flash by at a significant fraction of c. That's 4 phases.
Craziest I go is, if you still have control over the craft, swing it around Mars and bring it back to the Moon. If you can manage the really tight turns without aerobreaking in Mars' atmosphere, you could theoretically fly back and forth between Mars and the Moon until the thruster gives out. Eventually you'd be making transits in less than a day, and the thruster could well last for years. You want and need the data for duration flight so this final stage is actually more than a dramatic demonstration. It informs future thruster design work and makes the craft into a thruster lab all its own, out there contending with solar radiation and all sorts of other issues you'd like to get info on.
To do this, you need to steer the cubesat. It's got an array of hundreds of tiny thruster elements spread out laterally so you can steer the thing by switching them off. The question comes, how do you program such a thing? Is there anyone here who can comment on this task intelligently and say whether you think it even possible the GN&C here is capable of such a journey?
http://www.cubesatkit.com/
And who do you look for to develop such a system? Not just a "programmer". . .but what? How do you even screen people to see if they can do this kind of work?
Lets suppose you have a working, low thrust Mach-Effect Thruster that will fit into a cubesat, and you want to fly it around in deep space as part of a TRL7 demonstration of the technology. So you want to build a cubesat. And lets get crazy (because it's fun) and say that you have a radiation hardening technique you want to try out too, and if it works, you can fly through the Van Allen Belt unscathed. Since MET's don't run out of propellant, once you're clear of the VAB, you can go anywhere you'd like. You can for instance go cislunar. Cislunar is good. It's close enough to mother Earth that you can likely stay in touch and confirm the status of your spacecraft.
So that's 3 stages of mission. First to fly to equatorial orbit. Second to fly through the VAB. Third to fly to the Moon. And lets get all crazy and say forth you wrap around the moon, and fly off to Mars while its opposed to Earth. You cut across the system where there's lots of sunlight and say hello to NASA's first gen Elektra radio aboard the Mars Recon Orbiter as you flash by at a significant fraction of c. That's 4 phases.
Craziest I go is, if you still have control over the craft, swing it around Mars and bring it back to the Moon. If you can manage the really tight turns without aerobreaking in Mars' atmosphere, you could theoretically fly back and forth between Mars and the Moon until the thruster gives out. Eventually you'd be making transits in less than a day, and the thruster could well last for years. You want and need the data for duration flight so this final stage is actually more than a dramatic demonstration. It informs future thruster design work and makes the craft into a thruster lab all its own, out there contending with solar radiation and all sorts of other issues you'd like to get info on.
To do this, you need to steer the cubesat. It's got an array of hundreds of tiny thruster elements spread out laterally so you can steer the thing by switching them off. The question comes, how do you program such a thing? Is there anyone here who can comment on this task intelligently and say whether you think it even possible the GN&C here is capable of such a journey?
http://www.cubesatkit.com/
And who do you look for to develop such a system? Not just a "programmer". . .but what? How do you even screen people to see if they can do this kind of work?