Modifications

Sauter à la navigation Sauter à la recherche
3 272 octets supprimés ,  20 février 2022 à 00:34
Contenu remplacé par « {{ENG-CANSAT-NAV}} {{COMMON-CANSAT-FREQUENCY-PLAN}} {{ENG-CANSAT-TRAILER}} »
Ligne 1 : Ligne 1 :  
{{ENG-CANSAT-NAV}}
 
{{ENG-CANSAT-NAV}}
   −
== Forewords ==
+
{{COMMON-CANSAT-FREQUENCY-PLAN}}
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 collisions occurs.
  −
 
  −
Obviously, more we are talking on a same frequency, more we will have collision, 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.
  −
 
  −
== Suggested Frequency Plan ==
  −
  −
{| class="wikitable" border="1"
  −
|-
  −
| align="center" | '''Team'''
  −
| align="center" | '''Freq (MHz)'''
  −
| align="center" | '''Team name'''
  −
|- style="font-size: 90%"
  −
| align="left" | Team #1
  −
| align="left" | 433.1
  −
| align="left" | .                                                                                                                              .
  −
|- style="font-size: 90%"
  −
| align="left" | Team #2
  −
| align="left" | 433.2
  −
| align="left" |  
  −
|- style="font-size: 90%"
  −
| align="left" | Team #3
  −
| align="left" | 433.3
  −
| align="left" |  
  −
|- style="font-size: 90%"
  −
| align="left" | Team #4
  −
| align="left" | 433.4
  −
| align="left" |  
  −
|- style="font-size: 90%"
  −
| align="left" | Team #5
  −
| align="left" | 433.5
  −
| align="left" |  
  −
|- style="font-size: 90%"
  −
| align="left" | Team #6
  −
| align="left" | 433.6
  −
| align="left" |  
  −
|- style="font-size: 90%"
  −
| align="left" | Team #7
  −
| align="left" | 433.7
  −
| align="left" |  
  −
|- style="font-size: 90%"
  −
| align="left" | Team #8
  −
| align="left" | 433.8
  −
| align="left" |  
  −
|- style="font-size: 90%"
  −
| align="left" | Team #9
  −
| align="left" | 433.9
  −
| align="left" |  
  −
|- style="font-size: 90%"
  −
| align="left" | ...
  −
| align="left" | 434.0
  −
| align="left" | ...
  −
|}
  −
 
  −
== Frequency plan explained ==
  −
Why do we space the frequencies of 0.1 MHz (so 100 KHz)? Spacing more (>100 KHz) will be best, spacing less (<100 KHz) is not recommended.
  −
 
  −
The following capture coming from USA shows the spectrum view (and waterfall view) of a RFM69 emiting on the 868.0 MHz frequency.
  −
 
  −
{{ambox|text=Note: the 868.0 Mhz is a FREE ISM band in USA. In Europe, that frequency range is reserved for LoRa transmission!}}
  −
 
  −
[[Fichier:ENG-CANSAT-FREQUENCY-PLAN-10.png|640px]]<small><br />Source: [https://forum.mysensors.org/topic/11501/rfm69-range-issues this thread in the mysensors.org forum]</small>
  −
 
  −
[[Fichier:ENG-CANSAT-FREQUENCY-PLAN-11.png]]<small><br />Source: [https://forum.mysensors.org/topic/11501/rfm69-range-issues this thread in the mysensors.org forum]</small>
      
{{ENG-CANSAT-TRAILER}}
 
{{ENG-CANSAT-TRAILER}}
29 837

modifications

Menu de navigation