¶ Introduction
¶ Purpose, Objective and Scope
This document is separated in to two sections, the test specification and the test procedure.
The test specification section defines the purpose of the test, the test approach, the item under test, test sequence, test facility, pass/fail criteria, required documentation, participants and test schedule.
The test report section gives directions for conducting a test activity in terms of description, resources, constraints and provides detailed step‐by‐step instructions for conducting test activities with the selected test facility and set‐up.
This document covers the preparation and the procedure for qualification of full telecommunications pipeline --- radio boards with the patch antennas and motherboard.
This document provides the guidelines to the person performing the tests decribed hereinafter. It also covers both the testing protocol and the different points of analysis.
This document does not cover the actual analysis of the results, neither the test report.
¶ Test Documentation
There are 3 main types of types of documents which relate to testing activities.
¶ AI&T
- High level overiew of testing activities
- Highlights dependancies in between types of tests
- Tracks the status of each type of test
- Document should be prepared as early as possible after PDR
¶ TSP
-
Test specification section explains:
- What part/assembly is being tested during each test.
- What characteristic is being tested.
- Brief description as to how the test is goind to be conducted.
- Explains the Pass/Fail criteria for each step.
- Explains when the test is due to happen and who will be involved in the test.
-
Document should be prepared after the baseline AI&T and ~1 month before the actual test.
-
Test procedure serves as a detailed plan for each individual test, it contains (among other things):
- A list of tools and instrument needed for the test.
- A description of the test location and condition.
- A step by step procedure of what needs to be done before, during and after the test.
-
Document should be prepared after the test specification and at least ~1 week before the actual test.
¶ TR
- The test report contains:
- The "as run procedure", meaning the procedure as planned ~1 week before the test with all of the comments and modiciations which were done the day of the test.
- The results of the test and all of the test data (or at least a link to the test data).
- If applicable, the analysis of the test data.
- The conclusion.
- The baseline document should be prepared the day of the test and the final version should be ready ~1 week after the test
¶ Definitions and Abbreviations
- GS : Ground Segment
- GSC: Ground Segment Control
- RDB: Radioboard Unit
¶ Applicable and Reference Documents
ERT_RF_Protocol_Interface
2024_C_GS_GROUND-SEGMENT-CONTROL_DJF¶ Test Specification
¶ Open issue, Assumption and Constraint
The GSC's components --- MTHB, RBD and NUC --- are either remnents of the Nordend Mission or derived therefrom. As of writing, the state of those components is either partially known or unknown.
¶ Test Description
Objectives: (re)qualify the patch antennas, update status of each unit currently in the team's possession.
Methods: A single radioboard is setup in Tx mode and an SDR is setup with the full gnuradio pipeline. The patch anetnna is connected to the SDR.
Environment: No specific conditions are required.
Data and Scenarios: The transmitted data must be deterministically generated and each packet must be of a fixed size. The data WILL NOT abide by the ERT's standard packet format. The test shall be carried out under a half-duplex scheme.
Tools: Two computers.
¶ Test Sequence
No constraints on the testing activities sequence were identified.
¶ Pass/Fail Criteria
Data transmitted from the Rx to the Tx match the predicted sequence.
Packet Loss Rate is within the required range.
Range meets or exceed the required minimum.
Data transmitted from the Rx to the Tx does not match the predicted sequence.
Packet Loss Rate is outside the required range.
Range is below required minimum.
¶ Test Organisation
The test will be carried out by the TM and TL assigned to the Hardware of the GSC. It will take place once two fully-assembled RDB are available.
¶ Test Procedure
¶ Item Under Test
| Sub-System | Part Name/ID | Type of Part | Version ID |
|---|---|---|---|
| GS | Patch Antenna | FM | N/A |
| GS | Radioboard | FM | N/A |
| GS | Motherboard | FM | N/A |
¶ Test Equipment Checklist
| Packed ? | Equipment Set RDB Ground Station |
|---|---|
| RDB - Tx | |
| RDB - Rx | |
| Patch Antenna x2 | |
| RDB - MTHB Cable x2 | |
| MTHB | |
| MTHB - PC Cable | |
| PC |
| Packed ? | Equipment Set Control |
|---|---|
| RDB - Tx | |
| RDB Antenna | |
| RDB - PC Cable | |
| SDR (Dongle) | |
| SDR Antenna | |
| SDR - PC Cable | |
| PC |
¶ Test Instrumentation Description
Each computer must have the following setup
| Installed ? | Equipment |
|---|---|
| vscode + platformIO | |
| RDB codebase | |
| gnuradio | |
| SDR pipeline |
¶ Test Location and Conditions
The test's location is contingent upon the range of transmission
- For ranges below 1km, the tests shall be carried out at the Testing Facilitiy.
- For ranges beyond 1km, the tests shall be carried out at at any suitable place.
¶ Participants
| Responsible for: | Name |
|---|---|
| Equipment Sets Preparation | Noé |
| Equipment Sets Verification | Samuel |
| Transporation | Samuel |
| Documenting/Reporting | Noé |
| Preparing the test on-site | Samuel, Noé |
¶ Test Safety
¶ Main Risks
| Safety Concern | Probability | Impact | Severity | Mitigation | Post-Mitigation Probability | Post-Mitigation Impact | Post-Mitigation Severity |
|---|---|---|---|---|---|---|---|
| Rainfall; computer are not rated waterproof | D | 2 | D2 | Schedule multiple slots | C | 2 | C2 |
| Damage to a component | C | 4 | C4 | Bring backup on site (antennas, RDB, SDR, ...) | C | 1 | C1 |
¶ Main Hazards
| Safety Concern | Probability | Impact | Severity | Mitigation | Post-Mitigation Probability | Post-Mitigation Impact | Post-Mitigation Severity |
|---|---|---|---|---|---|---|---|
¶ Tasks and Step-by-Step Procedure
REMOVE THIS TEXT
This is the section where you give a detailed description of what needs to be done before during and after the test. It's broken up into 3 sections and 2 sub sections.
The 3 sections are what needs to be done before you start testing (for example: going through the operation procedure which is, preparing your assembly, ...), what needs to be done during the test (for example: how do you "reload" your test if you are redoing the test several times in the same day, how do you track/gather the data, ...) and what needs to be done after the test (for example: packing the fragile parts a certain way, analysing the data, ...).
The 2 sub-sections are: tasks ans step-by-step procedure. The difference in between the list of tasks and the step-by-step is that the tasks are simplified version of the step-by-step procedure. For example for a drop test, your tasks might be:
| Done ? | Task | Time | Operator |
|---|---|---|---|
| fold parachute | - | Marcus | |
| place parachute in deployment bag | - | Junius | |
| close deployment bag | - | Brutus | |
| place deployment bag on dron jig | - | Don Pablo |
And then for each of your tasks (or at least the most complicated onces) you would have a step by step procedure, for example folding the parachute could be:
| Done ? | Step | Tool |
|---|---|---|
| Fold each gore in half and stack them until you have a triangular stack of gores | - | |
| Put the parachute on the ground and remove all of the air | - | |
| Measure out the right length to fold the parachute (using the deployment bag) | - | |
| Fold in Z until the parachute is a rectangular stack | - | |
| Remove all of the air | - | |
| Roll the parachute as tight as possible from side to side (the lines should be on a side, not at the top or the bottom) | - | |
| CHECK | - | |
| Place the shock cord which attaches the deployment bag to parachute in the bag first | - | |
| Place the parachute in the deployment bag | - | |
| Place the cords and cables in the parachute bag in the shape of a bird's nest | - | |
| CHECK | - |
Tracking the time each step took will help you to better plan your future tests (You do not HAVE to track the time it took for each step).
Feel free to make the checklist on another application as long as links/images are included in this document.
REMOVE THIS TEXT
¶ Before Test
¶ Tasks
| Done ? | Task | Time | Operator |
|---|---|---|---|
¶ Step-by-step procedure
| Done ? | Step | Tool |
|---|---|---|
| - | ||
| - | ||
| - |
¶ During Test
¶ Tasks
| Done ? | Task | Time | Operator |
|---|---|---|---|
¶ Step-by-step procedure
| Done ? | Step | Tool |
|---|---|---|
| - | ||
| - | ||
| - |
¶ After Test
¶ Tasks
| Done ? | Task | Time | Operator |
|---|---|---|---|
¶ Step-by-step procedure
| Done ? | Step | Tool |
|---|---|---|
| - | ||
| - | ||
| - |