Design application-level interfaces for new hardware, sensors, and subsystems.
Draft stand-in payloads.
Implement new communication methods for new operations goals.
Interface with new hardware.
Perform testing on FlatSat.
Develop software on FlatSat.
Minimize development on FM to preserve flash integrity.
Verify operations.
Upload the final software images.
Allow for remote software updates.
Below are the requirements that require changes to the Iris flight software system.
R-LIB-BUS-008: Bus shall have a star tracker
Include star tracker sensor/software integration
R-LIB-BUS-009: Bus shall have a reaction wheel or magnetorquers
R-LIB-BUS-012: Bus shall have an accuracy of 1 deg
R-LIB-BUS-014: Bus shall have a temperature compensation feature
R-LIB-BUS-015: Bus shall have a drift compensation feature
R-LIB-BUS-016: Bus shall have an error detection and reporting feature
R-LIB-BUS-019: CubeSat shall be able to measure its pointing accuracy
R-LIB-BUS-022: Bus shall provide feedback on pointing accuracy
R-LIB-BUS-023: Bus shall incorporate GPS to determine the CubeSat position
R-LIB-BUS-031: CubeSat shall have a mechanism to detect and correct any deviation from required stability
R-LIB-BUS-032: Bus shall downlink data to satellite relay within 8 hours of processing
R-LIB-BUS-035: Bus shall downlink data to satellite relay within 5 mins of completing data processing
R-LIB-BUS-036: CubeSat should have a TBD data transfer rate to satellite relay
R-LIB-BUS-037: Bus shall communicate via the use of a satellite relay
R-LIB-BUS-042: CubeSat shall undergo LEOP activities before commissioning
R-LIB-BUS-043: LEOP activities shall not exceed 3 monthsÂ
R-LIB-BUS-044: Commissioning activities shall include calibration of all CubeSat instruments
R-LIB-BUS-045: LEOP activities shall be planned and scheduled before the start of the commissioning activities
R-LIB-BUS-046: Commissioning activities shall be planned and scheduled before the start of LEOP activities
R-LIB-BUS-047: LEOP activities shall include testing of all subsystems
R-LIB-BUS-048: Commissioning activities shall include calibration of all instruments
R-LIB-BUS-054: System shall regularly monitor the CubeSat's orbit to ensure the deorbit plan is still achievable
R-LIB-MIS-006: Li Bus shall be capable of performing normal operations for a minimum of 18 months
R-LIB-BUS-057: CubeSat shall be designed with a redundancy plan in place to ensure 18 month mission life
R-LIB-BUS-058: CubeSat shall have the ability to receive software updates
R-LIB-BUS-060: CubeSat shall not handle payload data processing
R-LIB-BUS-001: LI Bus shall send telemetry data to the payload upon request at a rate of TBD
R-LIB-BUS-062: LI Bus shall be capable of receiving processed data from the payload at a rate of TBD
R-LIB-BUS-065: Bus shall not store raw payload data
R-LIB-BUS-067: Bus shall be able to transmit at least 120 40kB data packets per orbit
R-LIB-BUS-070: Bus shall be able to transmit two 400kB data packets per orbit
R-LIB-BUS-071: Bus shall be able to store TBD kB of processed data
R-LIB-BUS-076: Bus shall be capable of sending time accurate to 1 msec compared to the Bus clock
R-LIB-BUS-101: CubeSat shall have a system reliability of at least 80%
R-LIB-BUS-107: CubeSat shall be able to recover from a Power Control Unit reboot within 5 minutes
R-LIB-MIS-001: LI Bus shall accommodate a generic imaging/remote sensing payload
R-LIB-MIS-004: LI Bus shall be capable of communicating through a satellite relay