Difference between revisions of "Projects:2014S1-56 Inter-Satellite Links for CubeSats"
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
QB50 is a project consisting of 50 international double and tripe CubeSats. The CubeSats will have various scientific instruments on board to carry out atmospheric research within the lower thermosphere, between 200 - 380km altitude, which is the least explored layer of the atmosphere. There will be 3 sets of scientific equipment onboard that will be used for the research. Another purpose of the project is to study the atmospheric re-entry process. | QB50 is a project consisting of 50 international double and tripe CubeSats. The CubeSats will have various scientific instruments on board to carry out atmospheric research within the lower thermosphere, between 200 - 380km altitude, which is the least explored layer of the atmosphere. There will be 3 sets of scientific equipment onboard that will be used for the research. Another purpose of the project is to study the atmospheric re-entry process. | ||
| − | == Project | + | == Project Information == |
| + | [[File:Images.jpg|thumb|right|String of pearls constellation]] | ||
Our project aim is to design and implement intersatellite linking between satellites. In other terms this is passing information from one satellite to another until it hits the destination satellite which is in contact with the targeted ground station. | Our project aim is to design and implement intersatellite linking between satellites. In other terms this is passing information from one satellite to another until it hits the destination satellite which is in contact with the targeted ground station. | ||
| Line 10: | Line 11: | ||
The project will be using the MSP430 microcontroller range from Texas Instruments due to there low power outputs that will allow the low power budget to be achievable. The radio frequency chip that will be used is also made by Texas Instruments called the CC1120. This was chosen since it was easy to write software for the microcontroller and RF chip to communicate with each other. Also the RF chip has packet handling capabilities to combat the effect of high bit error rates. | The project will be using the MSP430 microcontroller range from Texas Instruments due to there low power outputs that will allow the low power budget to be achievable. The radio frequency chip that will be used is also made by Texas Instruments called the CC1120. This was chosen since it was easy to write software for the microcontroller and RF chip to communicate with each other. Also the RF chip has packet handling capabilities to combat the effect of high bit error rates. | ||
| + | |||
| + | === Project Approach === | ||
| + | [[File:Untitled2.png|300px|thumb|right|Proposed system model]] | ||
| + | The approach that was taken throughout the project was looking at a current complete internet model, the TCP/IP model, and applying this to a satellite network. The model splits the transmission into 4 different layers the transport layer, internet layer, data link layer and the physical (wireless) layer. | ||
| + | |||
| + | ==== Transport layer ==== | ||
| + | This layer is responsible for determining if the data has minimal errors, duplicate data is discarded and lost packets are resent. | ||
| + | |||
| + | ==== Internet layer ==== | ||
| + | This layer is responsible for determining the final destination satellite and how the information will be routed to this destination. | ||
| + | |||
| + | ==== Data link layer ==== | ||
| + | This layer is responsible for applying the final encapsulation of the packet from the higher level layers and putting them into frames that will be sent over the network. This layer also completes any error detection/correction. | ||
| + | |||
| + | ==== Physical layer ==== | ||
| + | This layer is what medium the information will be transmitted over. In the case of our project the physical layer is wireless radio communications. | ||
| + | |||
| + | ==== Packet structure ==== | ||
| + | [[File:Untitled3.png|500px|thumb|right|Packet breakdown]] | ||
| + | The packet structure that is transmitted is split into 2 separate sections, the header field and the data field. The header field will contain several signalling bytes that will be used to determine where and how the packet will need to go. The data field will will contain the data that is being transmitted. | ||
| + | |||
| + | The header field be 6 bytes and will contain: | ||
| + | * Source: The source of the packet | ||
| + | * Destination: The final destination of the packet | ||
| + | * Next Hop: The next hop in the route of the packet | ||
| + | * Packet ID: To see whether the packet is a duplicate | ||
| + | * Type: To distinguish between routing, data and acknowledgement packets | ||
| + | * Time to live: A counter on the amount of hops the packet has taken ensures the packet doesn't infinitely route through the network | ||
=== Work Breakdown === | === Work Breakdown === | ||
| Line 15: | Line 44: | ||
==== Robert Bulfon ==== | ==== Robert Bulfon ==== | ||
| − | * Design and Implementation of | + | * Design and Implementation of transport layer |
| − | * Design and Implementation of | + | ** Random multiple access |
| + | ** Packet handling | ||
| + | * Design and Implementation of internet layer | ||
| + | ** Routing table population | ||
| + | ** Choose shortest jump path | ||
==== Troy Maylin ==== | ==== Troy Maylin ==== | ||
* Design and Implementation of wireless link | * Design and Implementation of wireless link | ||
| + | ** Create packet | ||
| + | ** Transmission of packets | ||
| + | ** Receiving of packets | ||
=== Project Status === | === Project Status === | ||
| − | * | + | [[File:Untitled1.png|300px|thumb|right|Current system model]] |
| − | * | + | Currently the system is able to communicate on a two terminal link. The features that are applied: |
| − | * | + | * Duplicate packets are handled |
| + | * Timed out packets are handled | ||
| + | * Reliable packet transmission (data with acknowledgements) | ||
| + | |||
| + | The internet layer has been designed for but still needs to be implemented to ensure that the linking can take place | ||
== Future == | == Future == | ||
| − | + | As noted above in the conclusion the project wasn’t completed and therefore there is plenty of room for future work that will be able to be completed. These include: | |
| + | * The power consumption constraint that was put upon us at the beginning of the project wasn’t applied at any stage of the project. The hardware that was chosen is capable of low power states so this is a definite outcome can could be achieved. | ||
| + | * Completing the internet layer is essential future work on the project. At the moment the project only allows for two terminal communications and it needs to exhibit routing behavior. This routing behavior has been designed for it will just need to be implemented. | ||
| + | * A more efficient method of automatic repeat requesting could be implemented. Other automatic repeat requests that could be implemented are go-back-n or selective repeat. | ||
| + | * A more efficient method of multiple access such as time division multiple access could be implemented. This will increase the efficiency of the data that is moved through the network since there will be set times that the CubeSats will know when to transmit and receive. | ||
| − | |||
== Team == | == Team == | ||
| Line 38: | Line 81: | ||
=== Supervisors === | === Supervisors === | ||
* Associate Professor Michael Liebelt | * Associate Professor Michael Liebelt | ||
| − | * | + | * Associate Professor William Cowley |
== Resources == | == Resources == | ||
| − | * MSP430F2410 | + | * Texas Instruments MSP430F2410 |
| − | * | + | * Texas Instruments MSP430G2553 |
| − | * CC1120 | + | * Texas Instruments CC1120 V-Chip |
* Code Composer Studio | * Code Composer Studio | ||
* MSPDebug | * MSPDebug | ||
| Line 49: | Line 92: | ||
* UART to USB serial interface | * UART to USB serial interface | ||
* PC | * PC | ||
| + | * DC power supply | ||
Latest revision as of 15:43, 29 October 2014
QB50 is a project consisting of 50 international double and tripe CubeSats. The CubeSats will have various scientific instruments on board to carry out atmospheric research within the lower thermosphere, between 200 - 380km altitude, which is the least explored layer of the atmosphere. There will be 3 sets of scientific equipment onboard that will be used for the research. Another purpose of the project is to study the atmospheric re-entry process.
Contents
Project Information
Our project aim is to design and implement intersatellite linking between satellites. In other terms this is passing information from one satellite to another until it hits the destination satellite which is in contact with the targeted ground station.
Since a CubeSat is only 30x10x10 cm satellite there are constraints that need to be considered such as:
- Wireless space links having high bit error rates
- Low power budget
- String of pearls constellation
The project will be using the MSP430 microcontroller range from Texas Instruments due to there low power outputs that will allow the low power budget to be achievable. The radio frequency chip that will be used is also made by Texas Instruments called the CC1120. This was chosen since it was easy to write software for the microcontroller and RF chip to communicate with each other. Also the RF chip has packet handling capabilities to combat the effect of high bit error rates.
Project Approach
The approach that was taken throughout the project was looking at a current complete internet model, the TCP/IP model, and applying this to a satellite network. The model splits the transmission into 4 different layers the transport layer, internet layer, data link layer and the physical (wireless) layer.
Transport layer
This layer is responsible for determining if the data has minimal errors, duplicate data is discarded and lost packets are resent.
Internet layer
This layer is responsible for determining the final destination satellite and how the information will be routed to this destination.
Data link layer
This layer is responsible for applying the final encapsulation of the packet from the higher level layers and putting them into frames that will be sent over the network. This layer also completes any error detection/correction.
Physical layer
This layer is what medium the information will be transmitted over. In the case of our project the physical layer is wireless radio communications.
Packet structure
The packet structure that is transmitted is split into 2 separate sections, the header field and the data field. The header field will contain several signalling bytes that will be used to determine where and how the packet will need to go. The data field will will contain the data that is being transmitted.
The header field be 6 bytes and will contain:
- Source: The source of the packet
- Destination: The final destination of the packet
- Next Hop: The next hop in the route of the packet
- Packet ID: To see whether the packet is a duplicate
- Type: To distinguish between routing, data and acknowledgement packets
- Time to live: A counter on the amount of hops the packet has taken ensures the packet doesn't infinitely route through the network
Work Breakdown
The work has been broken down so that both are able to work on the project concurrently whilst in the end being able to integrate there software.
Robert Bulfon
- Design and Implementation of transport layer
- Random multiple access
- Packet handling
- Design and Implementation of internet layer
- Routing table population
- Choose shortest jump path
Troy Maylin
- Design and Implementation of wireless link
- Create packet
- Transmission of packets
- Receiving of packets
Project Status
Currently the system is able to communicate on a two terminal link. The features that are applied:
- Duplicate packets are handled
- Timed out packets are handled
- Reliable packet transmission (data with acknowledgements)
The internet layer has been designed for but still needs to be implemented to ensure that the linking can take place
Future
As noted above in the conclusion the project wasn’t completed and therefore there is plenty of room for future work that will be able to be completed. These include:
- The power consumption constraint that was put upon us at the beginning of the project wasn’t applied at any stage of the project. The hardware that was chosen is capable of low power states so this is a definite outcome can could be achieved.
- Completing the internet layer is essential future work on the project. At the moment the project only allows for two terminal communications and it needs to exhibit routing behavior. This routing behavior has been designed for it will just need to be implemented.
- A more efficient method of automatic repeat requesting could be implemented. Other automatic repeat requests that could be implemented are go-back-n or selective repeat.
- A more efficient method of multiple access such as time division multiple access could be implemented. This will increase the efficiency of the data that is moved through the network since there will be set times that the CubeSats will know when to transmit and receive.
Team
Group members
- Mr Robert Bulfon
- Mr Troy Maylin
Supervisors
- Associate Professor Michael Liebelt
- Associate Professor William Cowley
Resources
- Texas Instruments MSP430F2410
- Texas Instruments MSP430G2553
- Texas Instruments CC1120 V-Chip
- Code Composer Studio
- MSPDebug
- MSPGCC
- UART to USB serial interface
- PC
- DC power supply
