This page contains a list of verification activities and links their evidence.

Verified Activities

Activities that were verified during Phases A, B, C, or D

V-COM-0001

Review datasheets for selected components of the communications system to verify lifetime of at least 3 months in space environment conditions.

Verified: Phase C, review by design

Evidence:The parts are (1) automotive grade, (2) the AEC200 automotive grade has been tested for up to 5 g's vibrations for 20 minutes, repeated for 12 cycles in 3 different orientations and can withstand -50° C to 125° C temperature range. (3) the link to the BOM is to show what parts were used for comms and all parts were hyperlinked to the part suppliers, where the datasheet can be found. Ref to AEC-Q200. The buck converter belongs to the Enhanced Product [EP] that has been tested for high-reliability material set. References to the Electrical BOM & datasheet

V-COM-0002

Check the team member registry and work packages and verify that the work is led by students

Verified: review by design, Phase C

Compliance Notes: Designed by Valoire, Aref & MB.

Evidence: Final design iteration done my Aref. Playbook and Wiki is used as evidence. See Team Registry and RACI Graph.

V-COM-0003

Review documentation for components that are being selected for grade (military or automotive) or contact the manufacturer for qualification documentation

Verified: by inspection, Phase C

Compliance Notes: Individually check each component datasheet (AEC-Q200 for Automotive Grade), automotive grade buck Converter alternative wasn't available for our application. The buck converter belongs to the Enhanced Product [EP] that has been tested for high-reliability material set. Pass/Fail criteria is if the item belongs to the specified grade. Still awaiting to hear from ISED. Applied for Uplink (436.65 MHz) and Downlink (436.25 MHz)

Evidence: References to the Electrical BOM & datasheet.

V-COM-0010

Verify that the selected communication frequencies are allocated for amateur satellite link use by Innovation, Science and Economic Development Canada (ISED).

Partially Verified: Phase C

Evidence: Still awaiting to hear from ISED. Applied for Uplink (436.65 MHz) and Downlink (436.25 MHz). See IARU Application. The maximum bandwidth for Region 2 (CAN Service Area) from RBR-4 Issue 2 January 2014, page 5 is 12 MHz. We still fall below the bandwidth requirement.

V-COM-0020

Verify that the spacecraft communications (uplink and downlink) do not exceed the maximum bandwidth specified by ISED.

Partially Verified: Phase C

V-COM-0030

Measure spacecraft transmissions to verify that the bandwidth does not exceed restrictions by ISED from the S11 plot obtained for the Spectrum Analyzer by drawing a line at the -10dB gain.

Not Verified: Phase D

Evidence: Pass/Fail Criteria: From the S11 plot obtained for the Spectrum Analyzer, the bandwidth can be obtained after drawing a line at the -10dB gain.

V-COM-0050

Verify that any imported communications components comply with the import conditions imposed by government.

Verified: Phase C

Compliance Notes: All components on dijikey and suppliers report EAR99.

Evidence: EAR99 is a U.S controlled good. It generally doesn't require an export/import license for low technology items. See datasheet.

V-COM-0060

Review the transceiver datasheet to verify the ability to set a limit for transmission time on.

Verified: review by design, Phase B

Evidence: TX max time and TX inhibit are parameters that can be set on the transceiver to limit the transmission time. See page 21. [7.2: TX max time, 7.4: TX inhibit].

V-COM-0061

Review the FSW boot up code and parameter initiation and verify that the maximum transmitter ON time is equal to one orbit period, or until the next communication window.

Not Verified: Phase D, Functional

Compliance Notes: The transceiver will be in 'idle/listen mode' until the satellite is close to the communication window to receive commands from a GS and start transmission.

Evidence: The part that pertains to this verification activity has not been implemented on the FSW code yet.

V-COM-0062

Simulate a transmission mode period for the communications system and send a telecommand to cease emissions. After a period of silence, send another telecommand to re-initiate transmission and verify that the downlink continues.

Not Verified: Phase D, FLATSAT, Over Air RF

Compliance Notes: Simulation will emulate an actual GS using a SDR. Testing involves sending a command to have the ability to stop and start communication. Dummy data packets can be used in this case. For reference RDP will be enabled to handle packets losses in actual data transmission.

V-COM-0063

Review the manual to ensure that a cessation or turn off of transmissions will not cause the radio to stop listening, or go into the mode that inhibits it to restart transmissions if telecommanded.

Verified: review by design, Phase B

Compliance Notes: The transceiver has an inbuilt Flash memory that doesn't get erased in case of a restart. The AX100-U manual is found here.

V-COM-0064

While the radio has ceased emissions due to a telecommand in V-COM-0062, reboot the CubeSat and check if the transmissions reoccur.

Not Verified: Phase D, Functional

V-COM-0065

Review the transceiver datasheet to verify that parameters and cessation commands are not wiped or reset when the system is rebooted.

Verified: Phase C

Evidence: Parameters are saved on the transceivers memory and doesn't get wiped on reboot/power cut. See example on page 21 [7.4: TX inhibit].

V-COM-0066

Test the transceiver to verify that parameters and cessation commands are not wiped or reset when the system is rebooted.

Not Verified: Phase D, FLATSAT

Evidence:

V-COM-0070

Verify that the frequency license applications are done properly with accurate information on the communications system while coordinating with RAC and IARU for the application submission.

Verified: Phase C, review by design

Evidence: IARU application , verified by MB, Phil, Yujia & Levente Buzas

V-COM-0071

Check the communications system design so that all downlink and uplink transmissions use amateur radio UHF frequencies (430- 440Mhz).

Verified: review by design, Phase B

Evidence: The Uplink and Downlink frequency are related to amateur frequency band. See Link Budget. See AX-100 U Qualification documents for the operable range of the transceiver within the UHF band.

V-COM-0072

Review the communications design and check that there is one antenna that is designed to communicate in UHF frequencies.

Verified: review by design, Phase B

Evidence: See antenna design page on the wiki and communication design.

V-COM-0080

Test data transmission of the flatsat deployed antenna model and test the functionality of the antenna with transmission with the on-board transceiver.

Not Verified: Phase D, FLATSAT

Compliance Notes: A dummy data packet/beacon can be used to check proper transmission.

V-COM-0090

Review the data link layer protocol selected and verify that it is recognized / documented.

Verified: Phase B

Evidence: Transcievers using AX.25 and Cubestat Space Protocol (CSP). See pages 29-33.AX.25 is a popular data link layer protocol amongst amateur radio operators. See this blog and it lists all satellite that uses AX.25 standard.

V-COM-0100

Send a telecommand to the flatsat with both using an approved and non-approved callsigns and verify that it processes the approved callsigns and rejects commands from non-approved callsigns.

Not Verified: FLATSAT, Phase D

Compliance Notes: The FSW needs to perform a callsign check. Additional read about callsigns. The callsign can be modified and the FSW can check/reject any unapproved call sign embedded in the AX.25 data frames.

V-COM-0101

Test the FSW code and verify that there exists code that checks the AX.25 data header for the callsign . FSW code checks for the telecommand and callsigns and compares it to a list of approved callsigns. Approved callsigns shall accept the command while non-approved ones reject it.

Not Verified: Phase D, Integration Functional

Evidence: The part that pertains to this verification activity has not been implemented on the FSW code yet.

Compliance Notes: Within the OSI model, the AX.25 is the data link and CSP is the transport layer, within the AX.25 frame, it contains the callsigns sent along from GS.