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
Drones in a swarm using the same radio must also be on the same channel for proper communication. While this is documented in some places, it’s easy to miss, especially if you're relying on examples rather than reading the documentation. You might modify URIs without realizing this and then seeing communication break down.
This is something that frequently pops up on GitHub discussions.
I suspect this confusion arises more often due to the nature of addressing. In our client, for instance, users are encouraged to differentiate drones by channel rather than radio address. However, for swarm communications to work correctly, this approach should be reversed.
A simple solution I see right now is to just add inline comments above all listed URIs in the examples.
The text was updated successfully, but these errors were encountered:
Drones in a swarm using the same radio must also be on the same channel for proper communication. While this is documented in some places, it’s easy to miss, especially if you're relying on examples rather than reading the documentation. You might modify URIs without realizing this and then seeing communication break down.
This is something that frequently pops up on GitHub discussions.
I suspect this confusion arises more often due to the nature of addressing. In our client, for instance, users are encouraged to differentiate drones by channel rather than radio address. However, for swarm communications to work correctly, this approach should be reversed.
A simple solution I see right now is to just add inline comments above all listed URIs in the examples.
The text was updated successfully, but these errors were encountered: