## Further improvements » History » Version 11

« Previous -
Version 11/36
(diff) -
Next » -
Current version

*RIBAS MACHADO, Ederson , 03/22/2015 04:19 PM *

# Further improvements¶

As we have seen, the link budget equations can become very complex and, during the two months we have had to develop this project, sometimes we have had to do some assumptions in order to simplify the calculus and thus achieve a coherent software tool.

At the beginning of the project we did a long list of all possible options and features that could be included in a link budget tool, selecting them by order of priority in order to implement them.

Finally, in this last part is shown a list of other features and improvements that could be performed for future students.

### SERVICE¶

- Increase the possibilities of $BER$ and corresponding $\frac{Eb}{No}$ and Code gains. Our possible modulation applied is based in a table of the situation of Quasi-error-Free. As seeing in the figure below, from [1].Quasi-error-free (QEF) means that we will have less than one uncorrected error event per hour, for this table this situations correspond to a PER (Packet error ratio - relative to the symbols) about $10^{-7}$ .

<div style="margin-left: auto; margin-right: auto; width: 50em">Figure 1 - Table applied in SatLinkTool, Quasi-error-free situation, from reference [1].

</div>

We would like to add others situations like the for a situation without FEC, when code rate = 1. We have already start this implementation. In the first steps we'we implemented, for QPSK,BPSK, 8PSK, 16PSK and 32PSK, the graphic of $BER$ x $\frac{Eb}{No}$. One idea, is take the value of $\frac{Eb}{No}$ from a user input of $BER$, and then, perform the calculations. This implementations in labview can be see below.

<div style="margin-left: auto; margin-right: auto; width: 50em"> Figure 2 - Possible reference application to further increase of $BER$ possibilities </div>

To take the $$ value from a $BER$ input, we can explore matlab functions like solve

### PAYLOAD¶

We have develloped the first step to calculate the total depointing angle. One further improvements is finalize this implementation.

# REFERENCES¶

[1]