Implementation » History » Version 13
Version 12 (SERRA FONT, Anna, 03/17/2015 04:45 PM) → Version 13/74 (SERRA FONT, Anna, 03/18/2015 11:16 AM)
h1. Implementation
At this point we were familiar with the system analyse of a link budget, knowledge acquired throughout the different subjects imparted in the master course and especially thanks to the realisation of the project 2 (_Design of a regional multi-beam satellite system_), that has an strong bond with the present project.
h2. Diagram block of application development
The diagram below shows the planning with the different phases we have designed in order to perform the successful and coherent development of the tool.
p=. !{width: 70%}figure4.jpg!
In short, the first steps were to decide what would be the basic structure of our link budget program and identify all the parameters and possible calculations, as well as the logical place to perform them in this structure. Thus, a preliminary design with the fundamental and simplest conditions has been would be performed, to then add gradually other features in order to improve its capabilities. Finally, verification of results and testing with subjects has been would be done in order to finish the complete design of the tool. These steps are further explained below.
It is known that link budget equations can become messy and complex and this calculus involve several aspects and conditions, furthermore, link budget can be analysed from different points of view. Globally, it can be defined with the following approaches:
* The first approach is a feasibility study: The user gives the features of the system, the targeted service, the bit rate, the bit error rate, etc., and the link budget says either if it is possible with this margin or if this is not possible (negative margin).
* In the second approach the user also defines the features of the system, and then the link budget says what is possible to do in terms of bit rate, bit error rate, etc.
* Finally there is a third approach where the user says which is the service he would like to have, and the link budget tool finds all the system settings. But this approach is much more complex, because as there are several parameters to define, it turns into a lot of different configuration options.
link budget es muy complejo --> desglosar e ir por etapas
The idea was to at first design the main link budget.
h2. Overview Application Plan
In order to design a tool to help with the comprehension of the link budget in Link Budget analysis, firstly it is necessary to identify the topology of the satellite system communication system and divide it in block groups.
The division was made taking into account the path of the signal and the equipment, as well as the service provide. The divisions are: Geometry System, uplink, payload, downlink, service & overall link.
Looking for a good way to show the groups we've decided to show ¿...?¿? {TODO}
Just a little introduction: we have distributed our tool in 6 tabs: Geometry System, uplink, payload, downlink, service & overall link
In the following pictures we present a first implementation (they are sketches) for the tabs:
At this point we were familiar with the system analyse of a link budget, knowledge acquired throughout the different subjects imparted in the master course and especially thanks to the realisation of the project 2 (_Design of a regional multi-beam satellite system_), that has an strong bond with the present project.
h2. Diagram block of application development
The diagram below shows the planning with the different phases we have designed in order to perform the successful and coherent development of the tool.
p=. !{width: 70%}figure4.jpg!
In short, the first steps were to decide what would be the basic structure of our link budget program and identify all the parameters and possible calculations, as well as the logical place to perform them in this structure. Thus, a preliminary design with the fundamental and simplest conditions has been would be performed, to then add gradually other features in order to improve its capabilities. Finally, verification of results and testing with subjects has been would be done in order to finish the complete design of the tool. These steps are further explained below.
It is known that link budget equations can become messy and complex and this calculus involve several aspects and conditions, furthermore, link budget can be analysed from different points of view. Globally, it can be defined with the following approaches:
* The first approach is a feasibility study: The user gives the features of the system, the targeted service, the bit rate, the bit error rate, etc., and the link budget says either if it is possible with this margin or if this is not possible (negative margin).
* In the second approach the user also defines the features of the system, and then the link budget says what is possible to do in terms of bit rate, bit error rate, etc.
* Finally there is a third approach where the user says which is the service he would like to have, and the link budget tool finds all the system settings. But this approach is much more complex, because as there are several parameters to define, it turns into a lot of different configuration options.
link budget es muy complejo --> desglosar e ir por etapas
The idea was to at first design the main link budget.
h2. Overview Application Plan
In order to design a tool to help with the comprehension of the link budget in Link Budget analysis, firstly it is necessary to identify the topology of the satellite system communication system and divide it in block groups.
The division was made taking into account the path of the signal and the equipment, as well as the service provide. The divisions are: Geometry System, uplink, payload, downlink, service & overall link.
Looking for a good way to show the groups we've decided to show ¿...?¿? {TODO}
Just a little introduction: we have distributed our tool in 6 tabs: Geometry System, uplink, payload, downlink, service & overall link
In the following pictures we present a first implementation (they are sketches) for the tabs: