project:hgg:hardware:interface
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende ÜberarbeitungLetzte ÜberarbeitungBeide Seiten der Revision | ||
project:hgg:hardware:interface [2012-01-03 12:44] – 2.208.62.151 | project:hgg:hardware:interface [2016-01-13 09:21] – [Proposal for a dataformat for communication between groundstations and their connected computers] 87.17.102.42 | ||
---|---|---|---|
Zeile 2: | Zeile 2: | ||
Basically what I was thinking about was mostly the tracking of things, but I wanted to build a protocol in a way that the groundstations stay compatible for a deployment stage that enables them to send. This will surely not be the case for a while but still i'd like to think ahead. The main idea was that this kind of frame can be received and sent to the groundstation. For communication among groundstations over a satellite at least some kind of from adress field needs to be added. | Basically what I was thinking about was mostly the tracking of things, but I wanted to build a protocol in a way that the groundstations stay compatible for a deployment stage that enables them to send. This will surely not be the case for a while but still i'd like to think ahead. The main idea was that this kind of frame can be received and sent to the groundstation. For communication among groundstations over a satellite at least some kind of from adress field needs to be added. | ||
+ | |||
+ | I am thinking to use as communication software **" | ||
+ | |||
+ | See: | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | Antonio A. - ITALY - | ||
Zeile 7: | Zeile 15: | ||
^ Position ^ Length ^ Name ^ Meaning | ^ Position ^ Length ^ Name ^ Meaning | ||
- | | 0 | 32 | magic | magic id = 2 bytes, ' | + | | |
- | | 4 | + | | |
- | | 12 | 16 | protocol | + | | 6 | 16 | size | size of payload |
- | | | + | | 8 | 32 | chksum |
- | | | + | | |
- | | | + | | |
- | | | + | |
No idea if a magic would be really needed. Basically it's a simple frame format that can be used to implement sending and receiving with the groundstations and should thus be capable of handling different stages in the project. The frames can bei either sent over a serial cable or other device types (like ethernet, firewire or anything else) but still allows to control hardware inside the groundstation directly. | No idea if a magic would be really needed. Basically it's a simple frame format that can be used to implement sending and receiving with the groundstations and should thus be capable of handling different stages in the project. The frames can bei either sent over a serial cable or other device types (like ethernet, firewire or anything else) but still allows to control hardware inside the groundstation directly. | ||
- | ===== Hardware Adresses ===== | ||
- | Since we want to have a distributed network, we also need to think about how to send something over several hops and look into routing strategies in p2p networks. Knowledge about p2p networks and their protocol design is needed for this. I've been imagining a hardware adress based on the groundstation position and some random component - no idea if that' | ||
===== Protocols ===== | ===== Protocols ===== |
project/hgg/hardware/interface.txt · Zuletzt geändert: 2016-01-13 09:26 von 87.17.102.42