This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
doc:crazyflie:dev:arch:communication [2015-07-15 16:31] 127.0.0.1 external edit |
doc:crazyflie:dev:arch:communication [2021-06-24 16:36] (current) kimberly |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | <WRAP center round important 60%> | ||
| + | This page has deprecated and will be archived. Please go to [[https:// | ||
| + | </ | ||
| + | |||
| {{ : | {{ : | ||
| ====== Communication stack ====== | ====== Communication stack ====== | ||
| Line 9: | Line 13: | ||
| ===== Module ===== | ===== Module ===== | ||
| - | Each module is assigned a port, which works much like the ports in TCP. Sending data on a specific port will make sure it's routed to the registered module for this port. The data that is sent to/from a specific port also contains a channel id of 3 bits. This channel id can be used to more easily route the data once inside the module. | + | Each module is assigned a port, which works much like the ports in UDP. Sending data on a specific port will make sure it's routed to the registered module for this port. The data that is sent to/from a specific port also contains a channel id of 3 bits. This channel id can be used to more easily route the data once inside the module. |
| ===== CRTP ===== | ===== CRTP ===== | ||