Moderator: alexc
alexc wrote:By the way, if you and your team wishes, you can use our existing infrastructure (forum and wiki) for your nanosat project. We might be able to share designs for various subsytems - you never know.
alexc wrote:Indeed. Personally, I'd love to explore the possibility to gather several projects/programs under the same umbrella. The SourceForge of space? SpaceForge?
Our existing infrastructure consisting of the wiki and forum may not be scalable to this extent. That's why I hope we can get experience with the https://launchpad.net/ - I particularly like its feature to create teams and sub-teams, which pretty much reflects our current organization in groups, how bugs are shared across projects using shared components, etc. The whole infrastructure seems well geared towards community contributions.
thuvt wrote:For example we aim to complete the nanosat and launch it by the end of 2010, most likely before any launch attempt by team FredNet. We can take advantage of this chance to test the distributed ground station data collection system or even test flight a component? (currently we have some room for spare within the nanosat)
AndersFeder wrote:If we are favorized in the selection of which technology is validated for public funds then, yes, it do matter.
alexc wrote:If you can reproduce the technical solution you can repeat the whole mission, no? Otherwise I'm not sure I understand what you mean.
AndersFeder wrote:alexc wrote:If you can reproduce the technical solution you can repeat the whole mission, no? Otherwise I'm not sure I understand what you mean.
Perhaps I'm using the word 'mission' incorrectly, but I mean there is a development phase and an operations phase. Must both phases be commercially feasible to repeat, or only the operations phase?
AndersFeder wrote:So, could the Iranian government set up an Iranian GLXP team to demonstrate their nation's space capability, fund it 100%, and still win the prize, as long as the fruit of those funds are marketed subsequently?
thuvt wrote:@tristancho: that's what I meant. At the moment my team is discussing on the conceptual design of the nanosat and most of the components are COST devices. So if these components work with the nanosat, it can be used in the lunar bus or the lander with greater confident.
thuvt wrote:...
Communication:
- Main transceiver: dualband (2m/70cm) handheld transceiver Kenwood TH-D7AG with built-in AX.25 TNC
- Backup transceiver, beacon transmitter, DTMF decoder (used in emergency cases): TBD
Please feel free to have a look and let me know if you have any questions. Comments are also welcome
alexc wrote:I never personally though of using an OTS hand-held for onbard radio, but it sounds like an interesting idea if it provides all the required functionality like the TH-D7AG does. However, I am concerned about too much excess power and weight wasted in components that you do not need but cannot remove, e.g. display driver, audio amplifier (for speaker and microphone) and so on. In any case, I would compare it to other options like existing designs from prior cubesats - you can find many of them on the net.
thuvt wrote:On a side note, we also want to experiment with a more advanced transceiver (on a higher frequency) and the MHX2400 from Microhard seems to be a good choice http://www.microhardcorp.com/MHX2400.htm
tristancho wrote:MHX could be a good option. We have selected this transceiver for our Picosat design.
thuvt wrote:- As far as I know, higher frequency tends to be more absorbed by the atmosphere (free space path loss) so I wonder if the MHX920A outperforms the MHX2420 in reality? Is there any advantage of using frequency 2.4Ghz vs 900Mhz?
thuvt wrote:The event runs till Sunday and we expect to receive as many as 20,000 visitors, time for some PR
Return to Earth CCC (aka SKYNET 9)
Users browsing this forum: No registered users and 2 guests