Methodology¶

In this section, we describe the methodology used to develop the geostationary satellite channel emulator. In order to make easier to monitor the project progress, we divide the project into the following phases:

1. We learn the LabVIEW programming concepts with a tutorial in order to build a basic system.
2. We research an example of QPSK modulation from the LabVIEW Modulation Toolkit.
3. We develop a QPSK communication system based on the LabVIEW example:

• We develop one module for each of the main components of the communication system: transmitter, channel and receiver.
• We develop an additive white gaussian noise (AWGN) channel.
• We implement the propagation delay effect in the communication system.
• We add a tool to visualize the received symbol constellation.

4. We test and validate the developed QPSK communication system via simulations. Testing, debugging and documentation.
5. We write the preliminary report.
6. We study the LabVIEW FPGA Module in order to run the developed communication system on FPGA.
7. We integrate the DVB-S2 modems in our communication system by replacing the transmitter and receiver modules.

• The transmitter module is replaced by a DVB-S2 modem. Testing, debugging and documentation.
• The receiver module is replaced by a DVB-S2 modem. Testing, debugging and documentation.
• Both the transmitter and the receiver are replaced by DVB-S2 modems. Testing, debugging and documentation.

8. We learn the hardware architectures of lab devices, including the modem, NI PXIe and Ethernet switch.
9. We research an example of channel streaming modulation in the LabVIEW.
10. We learn the related software architecture for the initialization and configuration.
11. We modify and implement the Labview example for acquisition of the QPSK signal.
12. We test and validate the signal via visualization and monitoring. Testing, debugging and documentation.
13. We modify and implement the Labview example for noise and delay generation.
14. We test and validate the synchronization via visualization and monitoring. Testing, debugging and documentation.
15. We analysis the results and performance.
16. We write the final report.