Différences entre versions de « ENG-CANSAT-FREQUENCY-PLAN »
Sauter à la navigation
Sauter à la recherche
| Ligne 12 : | Ligne 12 : | ||
{| class="wikitable" border="1" | {| class="wikitable" border="1" | ||
|- | |- | ||
| − | | align="center" | Team | + | | align="center" | '''Team''' |
| − | | align="center" | Freq (MHz) | + | | align="center" | '''Freq (MHz)''' |
| − | | align="center" | Team name | + | | align="center" | '''Team name''' |
|- style="font-size: 90%" | |- style="font-size: 90%" | ||
| align="left" | Team #1 | | align="left" | Team #1 | ||
Version du 20 octobre 2021 à 20:23
Forewords
The RFM69 module and Packet Radio can do a lot to secure message transmission and message content (with the encryption key).
As for wired network (aka TCP/IP) the packet radio enclose your data into datagram before sending it over the air. This helps the hardware to detect error and possibly recover when colisions occurs.
Obviously, more we are talking on a same frequency, more we will have colision, less the communication will be efficient.
The best solution would be to use a frequency plan where each team receives its own frequency range like showed in the following table.
| Team | Freq (MHz) | Team name |
| Team #1 | 433.1 | . . |
| Team #2 | 433.2 | |
| Team #3 | 433.3 | |
| Team #4 | 433.4 | |
| Team #5 | 433.5 | |
| Team #6 | 433.6 | |
| Team #7 | 433.7 | |
| Team #8 | 433.8 | |
| Team #9 | 433.9 | |
| ... | 434.0 | ... |
Written by Meurisse D. from MC Hobby - License: CC-SA-BY.