You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is a simple graph of my idea about Ground Station, that allows 2 way communication with Cansat or rocket + possibility to listen live data all the time.
We will need 2 pairs of LoRa.
1 Pair will be like in Cansat 1.0, for constantly sending data from Cansat and receiving it on ground:
2 Pair will be for 2 way communication. Ground station could send commands to Cansat/Rocket e.g. deploy parachute, and receive confirmation of successful action. It could look like this:
The text was updated successfully, but these errors were encountered:
If we stick with LoRa E5, only way to use P2P is with TEST mode. This mode doesn't have any security built in, even showing ID of the device that is sending the message. Anybody who is listening on the same frequency could easily receive a message with command, copy that message and send it again. Adding own ID in the beginning of message is not helpful, because it could be copied too.
In that case, we should add some encryption and authorization. Unfortunately I'm not familiar with that topic, but a very basic idea of how this could be resolved is below:
This will require some decoding mechanism with common algorithm for both: Cansat and Ground Station. Also records of previous keys on Cansat side. But probably there are a lot of better ways to secure that, all ideas are welcome.
Here is a simple graph of my idea about Ground Station, that allows 2 way communication with Cansat or rocket + possibility to listen live data all the time.
We will need 2 pairs of LoRa.
1 Pair will be like in Cansat 1.0, for constantly sending data from Cansat and receiving it on ground:
2 Pair will be for 2 way communication. Ground station could send commands to Cansat/Rocket e.g. deploy parachute, and receive confirmation of successful action. It could look like this:
The text was updated successfully, but these errors were encountered: