WikiSat interview

[John Pritchard]

Questions...

The WikiWikiSat shares electronics with the Picorover.. Can it be said that the WikiWikiSat is a balloon test version of the PicoRover electronics?

The "Wikisat Balloon Recovery System" (WBRS) is an Android application.  Is this installable on any Google Android phone?  Or is your phone an unlocked developer unit?

I like your adoption of the "meetup" for "could be a launch, depending on our schedules".  Do you think that an all volunteer, open source methodology can achieve complex integrated space flight systems?


Are there any other subjects you think might be interesting for our first WikiSat article on ULSF?

cheers,
John



--
http://www.google.com/profiles/teamfrednet.john.pritchard

[Joshua]

Hi John,

We are talking about two different prizes. Each prize have a different team where the exception are Alex and me. In addition, this situation will repeat with Monroe. I do like this guy because he is open mind. I want work with him in the GLXP project but I don't want to fight due to we are opponents in the N-Prize. I think Monroe and me we are over these situations because both we have a clear target: reach the space instead of wing a prize.

 

The good of this you mentioned is we are using same components to build a satellite able to control a mini-launcher and changing the software able to control a PicoRover. I know that eZ430 is not the best solution for a mini-launcher or for a Lunar Rover but if we can reuse this hardware, we will speed-up the development and validation of both projects: Lunar Rover for GLXP and Mini-launcher/wikiwikisat for the N-Prize. To win is in a second plane.

The WikiWikiSat shares electronics with the Picorover.. Can it be said that the WikiWikiSat is a balloon test version of the PicoRover electronics?

Balloon flight is for test open hardware to be used in many open projects like N-Prize and GLXP.

 

The "Wikisat Balloon Recovery System" (WBRS) is an Android application.  Is this installable on any Google Android phone?  Or is your phone an unlocked developer unit?

Anders is the expert to answer this question. He uses Android 1.6 so I think could be used in any Android O.S based phone. Other think is the procedure to use a phone in a Balloon flight that has to be validated what we are doing with the HTC magic.That way we will avoid faults like the last balloon launch. It is interesting, in open projects, see how people try to avoid responsibility when somthing fails.

 

I like your adoption of the "meetup" for "could be a launch, depending on our schedules".  Do you think that an all volunteer, open source methodology can achieve complex integrated space flight systems?

This balloon flight was designed to demonstrate / to learn how an small team from different countries can work in a complex project like a mini-launcher. Change balloon for mini-launcher and you will have a complex launch. I know that balloon launch is no so complicated. In fact two persons can do it but we want to split the project and trust one each other. Alex have the responsibility of the ground station. Tobias have the responsibility of build the structure. Anders have the responsibility to program the recovery system. Sonia have the responsibility of to take coverage of the events. Joshua have the responsibility of the electronics. Each one have a part of the cake to work with. If any part fails, the cake lose beauty but still a cake.

 

Are there any other subjects you think might be interesting for our first WikiSat article on ULSF?

 

Yes, the key of success is KISS. We have to keep the team small otherwise it will be to complex to manage. I have some theories for this kind of open source project called MOLECULE. Molecule is a way to manage a team and is able to scale. This concept is based on the atom (a person) and the radical (a function) and every together forms the molecule (the small team). The schema of this concept follows an organic structure.

- When you start a project you have only one Carbon atom. This atom is the only atom that can't be replaced during all the project (this is the weak part).

- When the project increases this Carbon atom form a simple molecule with four more Hidrogens (Methane molecule). This small group forms a function. Hidrogens are in charge or realize small tasks commanded by the Carbon. If any Hidrogen fails, the Carbon will realize the task so Carbon don't need Hidrogens but the work will be too slow (this is the robust part).

- When the project increases a bit more, one of this Hidrogens change to Carbon and adds two Hidrogens forming a molecule called polymer (Ethane, Propane, etc.). This molecule can grow as much as required and can be adapted to the number of functions that the project requires (Following any IUPAC nomenclature).

- When the project is at the end we fire Hidrogens and converting Carbons into Hidrogens.

- Finally everything ends with only one atom and the project conclude or remains in standby because some time there are projects that requires to continue after many years since the project was stopped. In this case this main atom will start the process again.

 

Best,

Joshua

PS: You can elaborate if you wish an article for the ultralight web based on these questions.

[John Pritchard]

Hi,

We are talking about two different prizes.

The ULSF is about whatever's happening in the world at large..

The good of this you mentioned is we are using same components to build a satellite able to control a mini-launcher and changing the software able to control a PicoRover. I know that eZ430 is not the best solution for a mini-launcher or for a Lunar Rover but if we can reuse this hardware, we will speed-up the development and validation of both projects: Lunar Rover for GLXP and Mini-launcher/wikiwikisat for the N-Prize. To win is in a second plane.

Right, so the TI MSP430 is another proc from the ARM that is the standard for Team FREDNET and AMSAT, as well as Arduino projects.  It looks good, inexpensive and low power and has a convenient GCC target.  Are you using GCC for your MSP430 software work?

I like your adoption of the "meetup" for "could be a launch, depending on our schedules".  Do you think that an all volunteer, open source methodology can achieve complex integrated space flight systems?

This balloon flight was designed to demonstrate / to learn how an small team from different countries can work in a complex project like a mini-launcher. Change balloon for mini-launcher and you will have a complex launch. I know that balloon launch is no so complicated. In fact two persons can do it but we want to split the project and trust one each other. Alex have the responsibility of the ground station. Tobias have the responsibility of build the structure. Anders have the responsibility to program the recovery system. Sonia have the responsibility of to take coverage of the events. Joshua have the responsibility of the electronics. Each one have a part of the cake to work with. If any part fails, the cake lose beauty but still a cake.

This is very interesting.  We've discussed the launcher, an idea in development.  Is there one launcher idea in your mind that is common to both WikiSat and Home Made Launcher?  I think you've mentioned an air launch idea, and I think you've written about a ground launch idea.

 

Are there any other subjects you think might be interesting for our first WikiSat article on ULSF?

 

Yes, the key of success is KISS. We have to keep the team small otherwise it will be to complex to manage. I have some theories for this kind of open source project called MOLECULE. Molecule is a way to manage a team and is able to scale. This concept is based on the atom (a person) and the radical (a function) and every together forms the molecule (the small team). The schema of this concept follows an organic structure.

- When you start a project you have only one Carbon atom. This atom is the only atom that can't be replaced during all the project (this is the weak part).

- When the project increases this Carbon atom form a simple molecule with four more Hidrogens (Methane molecule). This small group forms a function. Hidrogens are in charge or realize small tasks commanded by the Carbon. If any Hidrogen fails, the Carbon will realize the task so Carbon don't need Hidrogens but the work will be too slow (this is the robust part).

- When the project increases a bit more, one of this Hidrogens change to Carbon and adds two Hidrogens forming a molecule called polymer (Ethane, Propane, etc.). This molecule can grow as much as required and can be adapted to the number of functions that the project requires (Following any IUPAC nomenclature).

- When the project is at the end we fire Hidrogens and converting Carbons into Hidrogens.

- Finally everything ends with only one atom and the project conclude or remains in standby because some time there are projects that requires to continue after many years since the project was stopped. In this case this main atom will start the process again.

 

Yes, a cellular hierarchy.  This is definitely something we've learned about in our TF(X) efforts, that the whole of the GLXP problem can be overwhelming.  It's constructive to let the cells float free in the internet.


John

[Joshua]

Hi,

 

The ULSF is about whatever's happening in the world at large..

Agree

 

Right, so the TI MSP430 is another proc from the ARM that is the standard for Team FREDNET and AMSAT, as well as Arduino projects.  It looks good, inexpensive and low power and has a convenient GCC target.  Are you using GCC for your MSP430 software work?

We use Code Composer Esstentials but yes, GCC can be used as well.

 

This is very interesting.  We've discussed the launcher, an idea in development.  Is there one launcher idea in your mind that is common to both WikiSat and Home Made Launcher?  I think you've mentioned an air launch idea, and I think you've written about a ground launch idea.

There is two launchers behind:

- The first is an small launcher (less than 100 kg) to put in orbit the WikiWikiSat satellite. Uses only APCP propellant. This is for N-Prize

- The second is a bigger launcher (less than 2000 kg) to put on the Moon a Rover like PicoRover. Uses APCP for the launch and the Transfer Lunar Injection. Uses MCH biprop for landing on the Moon.This is for GLXP.

The first is covered by my Thesis the other is far in time.

Yes, a cellular hierarchy.  This is definitely something we've learned about in our TF(X) efforts, that the whole of the GLXP problem can be overwhelming.  It's constructive to let the cells float free in the internet.

Yes, float free.

 

Best,

Joshua

[Anders Feder]

Hi John,

man, 26 10 2009 kl. 11:52 -0400, skrev John Pritchard:
>
> Questions...
>
> The WikiWikiSat shares electronics with the Picorover.. Can it be said
> that the WikiWikiSat is a balloon test version of the PicoRover
> electronics?
>
> The "Wikisat Balloon Recovery System" (WBRS) is an Android
> application. Is this installable on any Google Android phone? Or is
> your phone an unlocked developer unit?

Yes, WBRS is installable on any Android phone. The phone used for
development is a standard HTC Magic, as is the 'flight model' actually
used aboard the balloon.

With a few minor exceptions, I've found that the standard API is more
than enough for our needs, and by staying out of low-level territory, we
reduce risk that some unforeseen circumstance cause our quite literally
"mission-critical" application to break something vital in the middle of
a flight.

The downside is that we don't have as fine-grained control over things
like application life-cycle (does stuff we are relying on suddenly get
garbage collected?) and power management (can we be certain that some
obscure service isn't draining the charge from the battery we need to
run on for the whole length of time until the device is recovered?), but
generally Google has designed the system intelligently enough to suit
our needs too.

Best regards,
Anders Feder

[John Pritchard]

So, one more question...

What functions will the satellite perform in orbit, and how? (I
imagine it's a kind of sputnik mission for 2009, "j'existe").

[John Pritchard]

Couple more questions...

There's both an ez430 and a `droid flying on the balloon, the droid
pair (flight and ground) is an independent recovery system for GPS.
The ez430 in orbit will communicate with the ground? on what
frequency / modulation / protocol ?

Is the sourcecode for your flight and recovery software online, yet?

[Joshua]

Yes. N-Prize sets a satellite may provide its position for at least 9 turns. Our approach (and has to be validated by N-Prize regulators) is to provide a code every turn, not all the time in order to save battery. A moment before the launch, N-Prize regulators will provide these codes.

Best, Joshua

[Joshua]

Abaut balloon flights, in addition to eZ430 transceiver (uses WIFI, 2.4 GHz) we will have two devices for tracking. The previous balloon flight was to validate the WBRS but we have to test again due to the in-flight fault. The other tracking system is an standar GPS-Radio transceiver using  APRS.
Best, Joshua

 

See Alex tracking idea:
I think we can get very simple and reliable real-time tracking by
using APRS (http://en.wikipedia.org/wiki/Automatic_Packet_Reporting_System).
It can be completely isolated from other systems. I already have a
suitable transmitter (~30g) that has RS232 input for GPS. The APRS
data is picked up by the already existing stations and goes directly
into the internet, see http://www.aprs.fi/
In the field, we don't use the internet, but receive the APRS data
directly using a dedicated receiver like the Kenwood TM-D710E, see
http://www.kenwood.eu/products/comm/radio_amateur/fm_mobile/TM-D710E/
The radio can even interface to an external device for plotting and
logging the received data.
We can test my transmitter Friday next week when I go for a drive.

[John Pritchard]

Another question, what's Sonia's last (family) name, and does she have a website or fb profile or so?

[Joshua]

Hi John,

 

Speak with her. This is the email:

Sonia.Perez-Mansilla AT upc.edu

My best,

Joshua Tristncho