The format was chosen by the Launch Provider; the video was saved from their stream, and I was in a hurry to put it up and didn't have a copy of Premier on hand to do transcoding.
FWIW, plays fine for me in mplayer.:)
Yea, the delays sorta threw a monkey wrench in Cal Poly's plan to use the operations from CP2 to help improve CP3's bus (CP3 is simply an evolution of CP2 with a different payload).
Cool to see so many other CubeSat developers popping out of the woodworks. I've done a bunch of software for CP3.:)
To be precise about it, the current launch was originally scheduled for October 2005, and is informally called the BelkA launch, due to its primary payload. The other launch, EgyptSat, is currently scheduled for September of this year (after over two years of delays now). The satellites were swapped in order to get the first set of satellites in orbit after such a long wait.
Just to set the record straight; CubeSats are not normally "built from a kit". There's a CubeSat kit available, but none of the 14 being launched are using it, and none of the 5 satellite on the next DNEPR launch use it.
It's a great kit, but it's not the only way CubeSats are made.:)
As educational projects, a lot of these groups (specifically the Cal Poly CPx crew) are focused primarily on giving students hands-on experience with actually researching, designing, building, testing, and (finally) operating a fully functional spacecraft. However, each satellite generally has a fairly significant payload; they're not "just junk".
For an example, check out the guys at Tokyo University; they've launched two cubesats now, one on the 2003 launch and one recently on SSETI (XV-IV and XV-V, respectively). They've got cameras on both--you can check out the pictures here: http://www.space.t.u-tokyo.ac.jp/cubesat/index-e.h tml
Slashdot Mirror
The format was chosen by the Launch Provider; the video was saved from their stream, and I was in a hurry to put it up and didn't have a copy of Premier on hand to do transcoding. FWIW, plays fine for me in mplayer. :)
Yea, the delays sorta threw a monkey wrench in Cal Poly's plan to use the operations from CP2 to help improve CP3's bus (CP3 is simply an evolution of CP2 with a different payload). :)
Cool to see so many other CubeSat developers popping out of the woodworks. I've done a bunch of software for CP3.
To be precise about it, the current launch was originally scheduled for October 2005, and is informally called the BelkA launch, due to its primary payload. The other launch, EgyptSat, is currently scheduled for September of this year (after over two years of delays now). The satellites were swapped in order to get the first set of satellites in orbit after such a long wait.
Just to set the record straight; CubeSats are not normally "built from a kit". There's a CubeSat kit available, but none of the 14 being launched are using it, and none of the 5 satellite on the next DNEPR launch use it. It's a great kit, but it's not the only way CubeSats are made. :)
As educational projects, a lot of these groups (specifically the Cal Poly CPx crew) are focused primarily on giving students hands-on experience with actually researching, designing, building, testing, and (finally) operating a fully functional spacecraft. However, each satellite generally has a fairly significant payload; they're not "just junk".
For an example, check out the guys at Tokyo University; they've launched two cubesats now, one on the 2003 launch and one recently on SSETI (XV-IV and XV-V, respectively). They've got cameras on both--you can check out the pictures here: http://www.space.t.u-tokyo.ac.jp/cubesat/index-e.h tml