|Name||Binar 1 (Binar-1)|
|Units or mass||1U|
|Status||Reentry 2022-09-30. Was semi-operational until 2021-11-02 (First heard about 2 weeks after launch when secondary beacon was commanded on, but final recorded transmission on that date according to SmallSat 2022 paper)|
|Deployer||J-SSOD (JEM Small Satellite Orbital Deployer)|
|Launcher||Falcon 9 (CRS-23)|
|Deployment||Deployed from ISS on 2021-10-12|
|Entity||Academic / Education|
|Launch brokerer||Space BD|
Test CubeSat technologies for deep space missions.
Develop an Australian capability in solar system exploration, with spacecraft built around a CubeSat platform for deep space missions.
Its mission goals are as follows:
5 days passed and we resided ourselves to the fact that maybe we couldn’t reach Binar. Then… 2 weeks later we heard back from the satellite after successfully enabling a secondary beacon!! So now what? Where do we go from here? We take what we learn and improve it for the next mission.
For example, we assumed the radio module we tested on the ground worked the same as the one we sent to space—but that wasn’t the case, leading to some frantic last-minute changes that eventually meant we didn’t get the images or data we hoped for from orbit.
|Failure cause||No signal until COTS communication system was put into its own beacon mode, which depleted the battery after 11.5 days. Most likely adapter board failure.|
|Sources||         |
|Photo sources||    |