29 887
modifications
Modifications
Sauter à la navigation
Sauter à la recherche
Ligne 2 :
Ligne 2 : − + Ligne 9 :
Ligne 9 : − + Ligne 71 :
Ligne 71 : − + + + + + + + + + + + Ligne 78 :
Ligne 88 : − But having multiple data in string representation is not enough, they must be organized. '''They final format must be easy to parse and very compact''' (smaller is the radio message and higher is the chance for him to get to the ground without error). + + + Ligne 146 :
Ligne 158 : − + Ligne 386 :
Ligne 398 : + + + + + + + + + + + + + + +
→The code explained
== Introduction ==
== Introduction ==
{{ambox|text=Before starting this point, we recommand to follow all the sensors testing steps (BMP280 sensor, TMP36 Sensor, RFM69HCW radio and RFM69HCW Testing).
{{ambox|text=Before starting this point, we recommand to follow all the sensors testing steps (BMP280 sensor, TMP36 Sensor, RFM69HCW radio, RFM69HCW Testing and onboard NeoPixel).
It contains all the details about the wiring, install needed libraries and conduct basic testing.}}
It contains all the details about the wiring, install needed libraries and conduct basic testing.}}
* Air temperature
* Air temperature
* Air pressure
* Air pressure
and transmissing the information via the RFM69HCW radio module.
and transmitting the information via the RFM69HCW radio module.
== Wiring ==
== Wiring ==
# Going autonomous (removing Serial Connexion waiting) + add the Lipo
# Going autonomous (removing Serial Connexion waiting) + add the Lipo
The code proposed here under has been tested up to 22620128 (22.6 millions) iterations without issue, time when we decided to ends the test :-) .
The code proposed here under has been tested up to 23197 iterations without issue, time when we decided to ends the test :-) .
Once uploaded to your Feather, open the Serial Monitor and set it to 9600 bauds. '''The sketch would wait until you open the Serial Monitor to start transmitting the data'''.
You should see the following messages appears on the Serial Monitor.
[[Fichier:ENG-CANSAT-MISSION1-CAPTURE-20.png]]
Where we could see the transmitted messages with the packetnum packet index, timing and data.
The screen also displays the '''ACK''' acknowledgement send back by the receiver.
== Structuring the data ==
== Structuring the data ==
So to transport the data to the receiver, we need to transform the values (float, integer) into their string representation.
So to transport the data to the receiver, we need to transform the values (float, integer) into their string representation.
When having multiple data in their string representation is not enough, they must also been organized.
'''The final format must be easy to parse and very compact''' (smaller is the radio message and higher is the chance for him to get to the ground without error).
We propose the following format:
We propose the following format:
== The code explained ==
== The code explained ==
Here some explanation about the {fname|mission1-serial-radio-capture.ino}} sketch used in the CanSat.
Here some explanation about the {{fname|mission1-serial-radio-capture.ino}} sketch used in the CanSat.
This Arduino sketch would:
This Arduino sketch would:
}
}
</syntaxhighlight>
</syntaxhighlight>
== Fault tolerant design ==
The goal is to transmit the data to the ground station.<br />The code of the Emitter (this section) and Receiver (next section) are doing the job.
However, what would happens to your data if the antenna did break? All the data are lots!
This is where the "Extra Flash" would be a great help!
As showed earlier, it is also possible to store/save the data into the Flash.
A good approach would be:
# to save the data in the Flash
# then send it over Radio.
In this way, the data stays available inside the CanSat and could be extracted as suited.
{{ENG-CANSAT-TRAILER}}
{{ENG-CANSAT-TRAILER}}