QB
Note:
CubeSat Name / Number
Lead Institute
Contact Person
Date
Reference Document
Version
Revision of Version 1
- Updated QB50-SYS-1.4.1 to define WOD.
- Updated QB50-SYS-1.5.4 to indicate the information to be included in telemetry downstream.
- Deleted QB50-SYS-1.5.10. The position accuracy requirement for the CubeSat is dependant upon the science sensor which
- Updated QB50-SYS-1.5.11 to state the additional information that should be provided through the beacon.
- Updated QB50-SYS-1.5.13 to state where the data type during downlink should be specified.
- Updated QB50-SYS-1.7.9 to remove uncertainty in the type of data that is to be sent to the QB50 storage server by the tea
- Added QB50-SYS-1.7.10.
- Added QB50-SYS-1.7.11.
- Added QB50-SYS-1.7.12
Revision of Version 2
- Updated QB50-SYS-1.1.8, 1.2.1, 1.4.1, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8, 1.5.7, 1.5.9,
1.5.14, 1.6.2, 1.7.3, 1.7.4, 1.7.5, 1.7.7, 1.7.8, 1.7.9,
- Added QB50-SYS-1.1.9, 1.4.9
- Recommendations added
- Added requirements from Calpoly Standard
Revision of Version 3
- Updated QB50-SYS-1.2.1, 1.4.1, 1.7.1, 1.7.11, 1.7.12
- Deleted QB50-SYS-1.5.12 (now Recommendation 15)
- Added QB50-SYS-1.7.13, 2.0.1, 2.9.2, 3.1.12
- Recommendations 13-20 added
- Updated Table numbers
- standardized the use of DPAC acronym
Requirement Number
Structural Subsystem
QB50-SYS-1.1.1
QB50-SYS-1.1.2
QB50-SYS-1.1.3
QB50-SYS-1.1.4
Recommendation 8
QB50-SYS-1.1.9
QB50-SYS-1.1.5
QB50-SYS-1.1.6
Recommendation 1
QB50-SYS-1.1.7
QB50-SYS-1.1.8
Attitude Determination and Control Subsystem (ADCS)
QB50-SYS-1.2.1
Recommendation 13
QB50-SYS-1.2.2
Recommendation 9
Recommendation 14
Electrical Power Subsystem (EPS)
QB-SYS-1.3.1
QB-SYS-1.3.2
QB-SYS-1.3.3
On-Board Computer (OBC) and On-Board Data Handling (OBDH)
QB50-SYS-1.4.1
QB50-SYS-1.4.2
Recommendation 10
QB50-SYS-1.4.3
QB50-SYS-1.4.4
QB50-SYS-1.4.5
QB50-SYS-1.4.6
QB50-SYS-1.4.7
QB50-SYS-1.4.8
QB50-SYS-1.4.9
Recommendation 11
Recommendation 2
Telemetry, Tracking and Command (TT&C)
QB50-SYS-1.5.1
QB50-SYS-1.5.2
QB50-SYS-1.5.3
QB50-SYS-1.5.4
Recommendation 3
Recommendation 4
QB50-SYS-1.5.5
QB50-SYS-1.5.6
QB50-SYS-1.5.7
QB50-SYS-1.5.8
QB50-SYS-1.5.9
QB50-SYS-1.5.10
QB50-SYS-1.5.11
Recommendation 12
QB50-SYS-1.5.12
Recommendation 15
QB50-SYS-1.5.13
QB50-SYS-1.5.14
Thermal Control
QB50-SYS-1.6.1
QB50-SYS-1.6.2
Recommendation 16
General
QB50-SYS-1.7.1
QB50-SYS-1.7.2
Recommendation 5
QB50-SYS-1.7.3
QB50-SYS-1.7.4
QB50-SYS-1.7.5
Recommendation 6
QB50-SYS-1.7.6
QB50-SYS-1.7.7
QB50-SYS-1.7.8
QB50-SYS-1.7.9
QB50-SYS-1.7.10
Recommendation 7
QB50-SYS-1.7.11
QB50-SYS-1.7.12
QB50-SYS-1.7.13
Recommendation 17
Q
QB50-SYS-2.0.1
QB50-SYS-2.1.1
QB50-SYS-2.2.1
QB50-SYS-2.2.2
QB50-SYS-2.3.1
QB50-SYS-2.4.1
QB50-SYS-2.5.1
QB50-SYS-2.6.1
QB50-SYS-2.7.1
QB50-SYS-2.8.1
QB50-SYS-2.9.1
QB50-SYS-2.9.2
Recommendation 18
Functional Tests
QB50-SYS-3.1.1
Additional requirements and recommendations on functional tests
QB50-SYS-3.1.2
Recommendation 19
Recommendation 20
End-to-End HIL Test
QB50-SYS-3.2.1
Requirement Number
2.1 General requirements
CDS-2.1.1
CDS-2.1.2
CDS-2.1.3
CDS-2.1.4
CDS-2.1.4.1
CDS-2.1.5
CDS-2.1.6
CDS-2.1.7
CDS-2.1.7.1
CDS-2.1.7.2
CDS-2.1.7.3
CDS-2.1.8
2.2 CubeSat Mechanical Requirements
CDS-2.2.1
CDS-2.2.2
CDS-2.2.3
CDS-2.2.4
CDS-2.2.5
CDS-2.2.6
CDS-2.2.7
CDS-2.2.8
CDS-2.2.9
CDS-2.2.10
CDS-2.2.11
CDS-2.2.12
CDS-2.2.13
CDS-2.2.14
CDS-2.2.15
CDS-2.2.16
CDS-2.2.17
CDS-2.2.18
CDS-2.2.19
CDS-2.2.20
CDS-2.2.21
2.3 Electrical Requirements
CDS-2.3.1
CDS-2.3.2
CDS-2.3.2.1
CDS-2.3.3
CDS-2.3.4
2.4 Operational Requirements
CDS-2.4.1
CDS-2.4.2
CDS-2.4.3
CDS-2.4.4
CDS-2.4.4.1
CDS-2.4.5.1
CDS-2.4.5
CDS-2.4.6
2.4 Testing Requirements
QB50 Requirements C
Please fill in the following table and append it with the QB50 AITRR/FRR Data
For any questions regarding this Compliancy Table please contact the following peop
QB50 System Requirements issue 7 and Calpoly CubeSat Design Specification rev12
version 3 - 16/02/15
o define WOD.
indicate the information to be included in telemetry downstream.
The position accuracy requirement for the CubeSat is dependant upon the science sensor which it is carrying and it is specified in the corre
o state the additional information that should be provided through the beacon.
o state where the data type during downlink should be specified.
remove uncertainty in the type of data that is to be sent to the QB50 storage server by the teams.
1.2.1, 1.4.1, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8, 1.5.7, 1.5.9,
7.5, 1.7.7, 1.7.8, 1.7.9,
.9
Calpoly Standard
.4.1, 1.7.1, 1.7.11, 1.7.12
now Recommendation 15)
0.1, 2.9.2, 3.1.12
dded
AC acronym
Requirement Text
CubeSat System R
CubeSats dimensions shall be as shown in Table 2.
The CubeSats shall use the reference frame as shown in Figure 1 such that it will be in line with the reference frame of the dep
In launch configuration the CubeSat shall fit entirely within the extended volume dimensions shown in Figure 3 for a 2U CubeS
any protrusions.
After integration into the deployer, the CubeSat shall only require access, for any purpose, through the access hatches in the d
dimensions of these hatches are shown in Figure 5.
It is recommended to have a connector that is smaller than 25 mm × 13 mm – which is the dimension of the access hatch – so t
Due to the wide range of possible solutions each team shall supply the required Electrical Ground Support Equipment (EGSE) a
The CubeSat mass shall be no greater than that shown in Table 3.
The CubeSat centre of gravity shall be located within a sphere of 20 mm diameter, centered on the CubeSat geometric centre.
For aerodynamic stability, it is recommended to have the CubeSat centre of gravity towards the face of the Science Unit (-Z fac
velocity direction) with respect to the CubeSat geometric centre.
Deployment switches shall be non-latching (electrically or mechanically).
The CubeSat rails and standoffs, which contact the QuadPack rails, pusher plate, door, and/or adjacent CubeSat standoffs, sha
cold-weld to any adjacent materials.
n and Control Subsystem (ADCS)
The CubeSat shall be able to recover from tip-off rates of up to 50 deg / sec within 3 days (nominal conditions).
The CubeSat shall be able to recover from tip-off rates of up to 90 deg / sec in off-nominal situation.
The Science Unit will be accommodated at one end of the CubeSat, on a 10 mm 10 mm face — the -Z face using the CubeSat r
vector
Teams normal to this face
using on-board GPSshall be inshould
receiver the spacecraft ramusage
foresee the velocity direction.
of GPS orbitalThe face shall
positions not be available
for improvement for solar
of early TLEscells,
withor foru
high
forward this face.
Magnetizable materials shall not be used for CubeSat parts.
ystem (EPS)
The CubeSat shall provide sufficient power at the appropriate voltage, either by solar array generation or battery, to meet the
subsystems in all modes of operation.
The CubeSat shall be able to be commissioned in orbit following the last powered-down state without battery charging, inspec
up to 8 months.
The CubeSat shall be powered OFF during the entire launch and until it is deployed from the deployment system.
OBC) and On-Board Data Handling (OBDH)
The CubeSat shall collect whole orbit data and log telemetry every minute for the entire duration of the mission, where whole
of parameters: time, spacecraft mode, battery bus voltage, battery bus current, current on regulated bus 3.3V, current on reg
subsystem temperature, EPS temperature and battery temperature. If the bus is not acquiring some of this data, the WOD sha
format is documented in the reference document [R05].
The whole orbit data shall be stored in the OBC until they are successfully downlinked.
The correctness of received WOD packages should be verified by teams on ground (e.g. using parameter range checks) prior to
Any computer clock used on the CubeSat and on the ground segment shall exclusively use Coordinated Universal Time (UTC) a
The OBC shall have a real time clock information with an accuracy of 500ms during science operation. Relative times should be
01.01.2000 00:00:00 UTC.
The onboard software (OBSW) shall not be allowed to override hardware inhibits such as the deployment switch. (This is not a
cord).
The OBSW shall protect itself against unintentional infinite loops, computational errors and possible lock ups.
The check of incoming commands, data and messages, consistency checks and rejection of illegal input shall be implemented
The OBSW programmed and developed by the CubeSat teams shall only contain code that is intended for use on that CubeSat
Teams shall implement a command to be sent to the CubeSat which can delete any SU data held in Mass Memory originating
parameter of the command.
It is recommended to avoid encapsulation of one protocol within another (e.g. AX.25 in CSP) to avoid increased overhead.
It is recommended for the CubeSats to have the capability to schedule future autonomous downlinks such that it would be com
ground station networks.
nd Command (TT&C)
VHF shall not be used for downlink.
If UHF is used for downlink, the CubeSat shall use a downlink data rate of at least 9.6 kbps.
If UHF is used for downlink, the transmission shall fit in 20 kHz at -30 dBc, measured without Doppler, but over the entire oper
All CubeSats shall have and make use of its unique satellite ID in the telemetry downstream.
It is recommended to implement BPSK or QPSK downlinks because of their spectral efficiency.
It is recommended to use different bands for uplink and downlink.
If VHF is used for uplink, it shall have a data rate no greater than 1.2 kbps.
If UHF is used for uplink, it shall have a data rate no greater than 9.6 kbps.
All CubeSats shall have the capability to receive a transmitter shutdown command at all times after the CubeSat’s deployment
QuadPack ejection.
Once a transmitter shutdown command is received and executed by the CubeSat, a positive command from the ground shall b
Power reset (e.g. following eclipse) should not re-enable the transmitter.
The CubeSat provider shall have access to a ground station which has the capability and permission to send telecommands thr
DELETED FROM ISSUE 4 SYSTEMS REQUIREMENTS DOCUMENT
The CubeSat shall transmit the current values of the WOD parameters and its unique satellite ID through a beacon at least onc
power budget permits.
The beacon should be transmitted every 10 seconds during LEOP phase to allow for multiple receptions of the beacon during a
determination and the identification of each CubeSat.
DELETED FROM ISSUE 7 SYSTEMS REQUIREMENTS DOCUMENT
If UHF is used for uplink, the radio receiver shall have an Adjacent Channel Rejection Ratio (ACRR) of at least 100 dB.
The CubeSat shall use the AX.25 Protocol (UI Frames). The data type during downlink shall be specified in the Secondary Statio
address field of the AX.25 frame. Science data shall be indicated using 0b1111 and Whole Orbit Data with 0b1110.
User-friendly and documented software consisting of a) CubeSat data Frames Decoder b) CubeSat data Packet Decoder and c)
radio amateur regulations shall be made available to VKI 6 months before the nominal launch date. This documented software
following the AMSAT regulations.
The CubeSat shall maintain all its electronic components within its operating temperature range while in operation and within
times after deployment.
The CubeSat shall survive within the temperature range of -10 degC to +50 degC from the time of launch until its deployment
Due to the lessons learned from the QB50 precursor campaign, it is recommended for all QB50 CubeSats to have a battery hea
The CubeSat shall be designed to have an in-orbit lifetime of at least 6 months.
The CubeSat shall not use any material that has the potential to degrade in an ambient environment during storage after asse
approximately 2 years.
All electronic assemblies and electronic circuit boards should be conformally coated.
The CubeSat shall withstand a total contamination of 3.1 mg/m^2 at all phases of the launch vehicle ground operation and in fl
The CubeSat shall withstand a maximum pressure drop rate of 3.92 kPa/sec.
If a CubeSat has any special requirement in terms of cleanliness, handling, storage or shipment, these shall be communicated
be approved by ISIS, 12 months before delivery of the CubeSat and also highlighted in the User Manual.
The CubeSats should have a dedicated case for transport and storage.
Apply Before Flight (ABF) items, including tags and/or labels, shall not protrude past the dimensional limits of the CubeSat exte
Figure 4) when fully inserted.
All Remove Before Flight (RBF) items shall be identified by a bright red label of at least four square centimetres in area contain
or “REMOVE BEFORE LAUNCH” and the name of the satellite (CubeSat QB50 ID) printed in large white capital letters.
The CubeSat QB50 ID (e.g. BE05) shall be printed, engraved or otherwise marked on the CubeSat and visible through the acces
The CubeSat provider shall transfer the whole orbit data and science data to the DPAC within 24 hours following reception on
All of the whole orbit data and science data downlinked to the ground shall be stored in the individual CubeSat server up to 6
mission.
It is recommended for CubeSat teams to adopt the Engineering Qualification Model - Flight Model (EQM-FM) approach in build
CubeSats carrying the standard atmospheric sensors shall be able to commence the science payload operations within one mo
The standard atmospheric sensors shall be operated every second day for a period of 60 days, starting one month after deploy
The science operation phase shall be resumed after the CubeSat constellation has reached an altitude of approximately 300 km
weeks ahead of the event. The standard atmospheric sensors shall be operated every second day
for a period of 60 days.
The standard atmospheric sensors shall be operated every day during the science phases, also in between the two science pha
maximize the science return.
Qualification and Acceptance Tes
The CubeSat shall be compatible with any local time of ascending node (LTAN).
CubeSat shall pass the acceleration (quasi-static) test as per Table 6.
The CubeSat shall pass a resonance survey test, the characteristics of which are stated in Table 6 and the lowest natural frequ
90 Hz.
Two resonance surveys shall be performed during the mechanical test campaign. One before and one after running a test at fu
three axes).
The CubeSat shall pass the sinusoidal vibration tests as per Table 8.
The CubeSat shall pass the random vibration tests as per Table 9.
The CubeSat shall pass the shock tests as per Table 10. The shock loads shall be applied two times along each axis.
The variation of natural frequencies measured in the two resonance surveys as per QB50-SYS-2.2.2 shall be lower than 5%.
The CubeSat shall pass the Thermal Vacuum Cycling tests as per Table 11.
The CubeSat shall pass the Thermal Vacuum Bake Out tests as per Table 12.
CubeSats subsystems and components shall not have electromagnetic emissions generating self-interferences with other subs
If during the functional test a potential self-interference will be identified, a complete EMC test in anechoic chamber shall be p
reported in Sections 2.9.1 and 2.9.2.
As per QB50-SYS-2.9.2, the verification of EMC through a dedicated test is not mandatory if no self-incompatibility is detected.
recommended: it can be done according to test levels and procedures defined in Sections 2.9.1 and 2.9.2, for radiated emission
Quality Assurance
The CubeSat functionalities shall be verified using the functional test sets reported in Table 12.
nts and recommendations on functional tests
The satellite flight software shall be tested for at least 14h satellite continuous up-time under representative operations.
The satellite flight software shall be tested for at least 30h satellite continuous up-time.
The ground station shall be tested with a satellite in orbit (preferably using the QB50 Precursor satellites) for up and downlink
procedure.
CubeSats boarding the QB50 Sensors Unit shall perform an End-to-End test, to verify the functionality of the sensors and the in
Detailed procedure will be given in the User Manual shipped with the Sensor Unit hardware. An overview of the testing proce
Requirement Text
CubeSat Design Specificatio
ents
CubeSats which incorporate any deviation from the CDS shall submit a DAR and adhere to the waiver process (see Section 1.3
All parts shall remain attached to the CubeSats during launch, ejection and operation. No additional space debris shall be crea
Pyrotechnics shall not be permitted.
No pressure vessels over 1.2 standard atmosphere shall be permitted.
Pressure vessels shall have a factor of safety no less than 4.
Total stored chemical energy shall not exceed 100 Watt-Hours.
No hazardous materials shall be used on a CubeSat. Please contact us if you are unsure if a material is considered hazardous.
CubeSat materials shall satisfy the following low out-gassing criterion to prevent contamination of other spacecraft during inte
Total Mass Loss (TML) shall be < 1.0 %
Collected Volatile Condensable Material (CVCM) shall be < 0.1%
Note: A list of NASA approved low out-gassing materials can be found at:
http://outgassing.nasa.gov
The latest revision of the CubeSat Design Specification shall be the official version (http://cubesat.calpoly.edu/pages/documen
developers shall adhere to.
al Requirements
Exterior Dimensions
The CubeSat shall use the coordinate system as defined in Figure 5. The –Z face of the CubeSat will be inserted first into the P-
The CubeSat configuration and physical dimensions shall be per Figure 5.
The CubeSat shall be 100.0+0.1 mm wide (X and Y dimensions per Figure 5).
A single CubeSat shall be 113.5+ 0.1 mm tall (Z dimension per Figure 5).
All components shall not exceed 6.5 mm normal to the surface of the 100.0 mm cube (the green and yellow shaded sides in Fi
Exterior CubeSat components shall not contact the interior surface of the P-POD, other than the designated CubeSat rails.
Deployables shall be constrained by the CubeSat. The P-POD rails and walls shall not to be used to constrain deployables.
Rails shall have a minimum width of 8.5mm.
The rails shall not have a surface roughness greater than 1.6 μm.
The edges of the rails shall be rounded to a radius of at least 1 mm
The ends of the rails on the +Z face shall have a minimum surface area of 6.5 mm x 6.5 mm contact area for neighboring Cube
At least 75% of the rail shall be in contact with the P-POD rails. 25% of the rails may be recessed and no part of the rails shall e
Mass
Each single CubeSat shall not exceed 1.33 kg mass.
Each triple CubeSat shall not exceed 4.0 kg mass.
The CubeSat center of gravity shall be located within a sphere of 2 cm from its geometric center.
Materials
Aluminum 7075 or 6061 shall be used for both the main CubeSat structure and the rails. If other materials are used the develo
waiver process.
The CubeSat rails and standoff, which contact the P-POD rails and adjacent CubeSat standoffs, shall be hard anodized aluminu
P-POD.
The CubeSat shall use separation springs (Figure 4) with characteristics defined in Table 1 on the designated rail standoff. Sepa
found using McMaster Carr P/N 84985A76. The separation springs provide relative separation between CubeSats after deploy
ments
No electronics shall be active during launch to prevent any electrical or RF interference with the launch vehicle and primary pa
fully deactivated during launch or launch with discharged batteries.
The CubeSat shall include at least one deployment switch on the designated rail standoff (shown in Figure 5) to completely tur
In the actuated state, the deployment switch shall be centered at or below the level of the standoff.
All systems shall be turned off, including real time clocks.
To allow for CubeSat diagnostics and battery charging after the CubeSats have been integrated into the P-POD all CubeSat um
designated Access Port locations, green shaded areas shown in Figure 5.
The CubeSat shall include a Remove Before Flight (RBF) pin or launch with batteries fully discharged. The RBF pin shall be remo
into the P-POD.
rements
CubeSats with batteries shall have the capability to receive a transmitter shutdown command, as per Federal Communications
All deployables such as booms, antennas, and solar panels shall wait to deploy a minimum of 30 minutes after the CubeSat's d
P-POD ejection.
RF transmitters greater than 1 mW shall wait to transmit a minimum of 30 minutes after the CubeSat's deployment switch(es)
Operators shall obtain and provide documentation of proper licenses for use of frequencies.
For amateur frequency use, this requires proof of frequency coordination by the International Amateur Radio Union (IARU). A
The orbital decay lifetime of the CubeSats shall be less than 25 years after end of mission life.
Developers shall obtain and provide documentation of approval of an orbital debris mitigation plan from the FCC or local agen
Cal Poly shall conduct a minimum of one fit check in which developer hardware shall be inspected and integrated into the P-PO
prior to launch. The CubeSat Acceptance checklist (CAC) shall be used to verify compliance of the specification (Appendix B for
CubeSats).
ents
All requirements supersed
ble v3
Davide Masutti
[email protected] Legend
Compliant Shall be compliant by PDR
Partially Compliant Shall be compliant by CDR
Non-Compliant (accepted waiver) Shall be compliant by FRR
Non-Compliant (pending waiver) Recommendations
Not Applicable
Compliancy Verification Action / Intent
Method
unch
Compliancy Verification Action / Intent
Method
nts
Not applicable
Not applicable
Title
Superseded by QB50-SYS-1.1.2
Superseded by QB50-SYS-1.1.1
Superseded by QB50-SYS-1.1.2
Not applicable
Superseded by QB50-SYS-1.1.3
Superseded by QB50-SYS-1.1.1
Superseded by QB50-SYS-1.1.1
Superseded by QB50-SYS-1.1.1
Title
Not applicable
Superseded by QB50-SYS-1.1.5
Superseded by QB50-SYS-1.1.6
Title
Superseded by QB50-SYS-1.1.8
Not applicable
Superseded by QB50-SYS-1.1.4
Not applicable
y PDR
y CDR
y FRR
ns
Date
Date
