QB50 System Requirements Document

More documents

Recommendations

Info

possibility of using other team’s ground stations. The software provided is extremely flexibleand individual teams can integrate their own specifics at many levels, for instance integratingtheir own payload-specific data processing or visualization.For the teams who chose to use the QB50 SCS, the packet and frame protocol is defined andthe teams will need to comply with it.1.5 Telemetry, Tracking and Command (TT&C)Note:** The requirements in section (1.5 Telemetry, Tracking and Command) should be taken asguidelines. If a QB50 ground station network is deemed necessary by the QB50 team, a moredefined set of TT&C requirements will be released in the near future.**Downlink frequency and data volumeQB50-SYS-1.5.1.If UHF is used for downlink, the CubeSat shall use a downlink datarate of 9.6 kbps.QB50-SYS-1.5.2.Each CubeSat carrying a set of standard QB50 science sensors shallcommunicate a volume of at least 2 Megabits of science data perday to the ground station that is operated by the universityproviding the CubeSat.In the case of a grounds station network, a volume of at least 8 Megabits (TBC before CDR) ofscience data per day shall be communicated to the ground station network. This ensures thereturn of a reasonable amount of science data. The total data volume transmitted to theground will be significantly higher as it includes not only science data but also data for theteams’ own experiment(s), housekeeping data, data for protocol overhead (AX.25, QB50 blockprotocol) and error detection / error correction (CRC, FEC, Interleaving).QB50-SYS-1.5.3.Each team shall ensure that their transmit frequency is stable tobetter than ±500Hz across all temperatures and operatingconditions, so that the entire transmit spectrum falls around theallocated centre frequency within the given bandwidth.This will help ensure that each satellite can be quickly identified even at the start of the missionwhen many or all of the spacecraft may be overhead a single ground station.QB50-SYS-1.5.4. If UHF is used for downlink, the transmission shall fit in 16 kHz at -30 dBc (measured without Doppler).Issue 3 12 5 February 2013
QB50-SYS-1.5.5.QB50-SYS-1.5.6.If UHF is used for downlink, frequency stability shall be better than10 ppm (TBC), over entire operating temperature range.Every downlink signal shall carry a unique identifier of whichsatellite is transmitting.This should be included as part of the data sent and should easily be readable even withoutextensive knowledge of the structure of the transmitted data.Recommendation 1 It is recommended to implement BPSK or QPSK downlinksbecause of their spectral efficiency.Recommendation 2 It is recommended to use different bands for uplink anddownlink.Recommendation 3 It is recommended to use CDMA as the downlink multiple accessscheme.Recommendation 4 It is recommended that all spacecraft should also have and makeuse of a national amateur radio call sign in the telemetrydownstream.Uplink frequency and telecommandsQB50-SYS-1.5.7.QB50-SYS-1.5.8.QB50-SYS-1.5.9.The CubeSat shall use an uplink data rate of 1.2 kbps.All CubeSats shall have the capability to receive a transmittershutdown command at all times later than 30 minutes after theCubeSat's deployment switches being activated from deployerejection.The CubeSat provider shall have access to a ground station whichhas the capability and permission to send telecommands throughan uplink to control its satellite and to upload and execute timedInstrument Command Files. The format of these commands is TBD.QB50-SYS-1.5.10. The CubeSat shall determine its position to within 1 km accuracy.Issue 3 13 5 February 2013
Page 1 and 2: QB50System Requirementsand Recommen
Page 4: Science Payload Interface Control D
Page 7 and 8: 1. CubeSat System Requirements1.1 S
Page 9: Figure 3: 3U CubeSat extended volum
Page 14 and 15: QB50-SYS-1.5.11. Every science pack
Page 16 and 17: 3. Display which ground station is
Page 18 and 19: 2.3 Spacecraft ContaminationQB50-SY
Page 22: 4.1 MechanicalAs shown in Figure 5,
Page 25 and 26: Attachment A: INMS Interface Contro
Page 27 and 28: CHANGE RECORDIssue Date Sections ch
Page 29 and 30: 5.9.4 OBC_SU_ON (0xFB) ............
Page 31 and 32: 2 Normative and Informative documen
Page 33 and 34: CUBESAT side connector to attach to
Page 35 and 36: 4.1.1 SWITCHED Power PinsThe +5, +3
Page 37 and 38: 4.4 Power BudgetThe power budget is
Page 39 and 40: 5.3 Command & Response Handling5.3.
Page 41 and 42: 5.4 Command Packet Structure to Sci
Page 43 and 44: 5.7 SU State Transition DiagramThe
Page 45 and 46: 5.9.2 Script TIME Field - @tTime-ta
Page 47 and 48: 5.9.9 SU_STIM (0x04)This command wi
Page 49 and 50: 5.9.12 SU_CALM (0x07)This command r
Page 51 and 52: 5.9.14 SU_HK (0x09)The HOUSE_KEEPIN
Page 53 and 54: 5.10 Example SU Command Sequence Sc
Page 55 and 56: 7 Attitude ControlThe CubeSat shall
Page 57 and 58: Attachment B: FIPEX Interface Contr
Page 59 and 60: FIPEX on QB50 Date: 06.02.2013--- D
Page 61 and 62: FIPEX on QB50 Date: 06.02.2013--- D
Page 63 and 64:
FIPEX on QB50 Date: 06.02.2013--- D
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Attachment C: m-NLP Interface Contr
Page 85 and 86:
TITLE: QB50 m-NLP Science Unit Inte
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
show all

QB50 System Requirements Document

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?