Phoenix CubeSat
Phoenix CubeSat
Phoenix CubeSat
Phoenix CubeSat
Phoenix CubeSat
Phoenix CubeSat
Phoenix CubeSat
Phoenix CubeSat
Name Phoenix CubeSat
Type CubeSat
Units or mass 3U
Status Semi-operational. Was operational until 2020-02-20, 1 day? 2-way comms possible, but science mission is not due to OBC failure (Smallsat 2020 and official website visited on 2020-09-25)
Launched 2019-11-02
NORAD ID 45258
Deployer NRCSD (NanoRacks CubeSat Deployer) [Quad-M]
Launcher Antares (ELaNa 25) (NG-12)
Deployment Deployed from ISS on 2020-02-19
Organisation Arizona State University
Institution University
Entity Academic / Education
Nation US
Launch brokerer Nanoracks
Oneliner Thermal imaging of cities to study spatial and temporal changes.
Results Phoenix's beacon was heard for the first time at a ground station located in Indonesia. Amateur operators continued to hear its health beacon throughout the day by tracking the ISS, including the Phoenix operations team, using the ASU ground station. The team was also able to perform a successful schedule uplink to collect more telemetry from the ADCS, which marked the first CubeSat operation from the university! Since deployment day, it has been difficult to hear from the spacecraft. During Phoenix's last pass of the day over the ASU ground station, the spacecraft went into an error state, which we believe depleted the battery below the voltage cutoff level. This would have cut power to the rest of the hardware, preventing the Phoenix from transmitting its health beacon, responding to our commands, or tracking the sun to generate more power.  It was discovered that while the AX100 transceiver was operational, the OBC did not respond to any packets beyond short ping commands. Further, ping communication only occurred successfully during daytime passes. This suggested that Phoenix was likely not tracking the sun using the ADCS, preventing the battery from charging sufficiently to power the spacecraft during eclipses. Upon further investigation into the error state, the anomalous stream of packets was linked to a syn-ack packet flood. Benchtop testing with an engineering model of the AX100 transceiver and conversations with the vendor indicate that a single bit flip in the packet checksum could have enabled the Reliable Data Protocol (RDP). This would have introduced the syn-ack stream in an effort to verify a link between the ground station and the spacecraft, resulting in a gradual drain of the battery level. However, while the packet stream issue is considered resolved, it is still unclear as to why we can only receive CSP ping packet responses from the OBC after the power reset.  Although Phoenix’s science objective was not achieved, the spacecraft can still be utilized for other purposes. The ability to conduct two-way communications allows the spacecraft to be useful for calibrating ground stations to communicate with CubeSats in LEO. 
Failure cause Uplink established, but bit flip in the radio and resulting stream of packets at the end of the first day depleted battery below voltage cutoff level. Afterwards OBC only responds to pings in daylight and the cause is unknown.
Sources [1] [2] [3] [4] [5] [6]

Last modified: 2020-12-27
Detailed Phoenix CubeSat entry in the Database
Full Nanosats Database (much more data)

Feel free to connect at any time.

Created by Erik Kulu


Social Platforms

LinkedIn: Nanosats
Twitter: @nanosatellites

Sister Websites

NewSpace Index:
Factories in Space:

Copyright © 2014 - 2021 Erik Kulu