Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Robust communication between robots #226

Open
SyrianSpock opened this issue May 14, 2019 · 3 comments
Open

Robust communication between robots #226

SyrianSpock opened this issue May 14, 2019 · 3 comments
Labels
high-priority High priority, should be fixed ASAP needs-hardware-testing
Milestone

Comments

@SyrianSpock
Copy link
Member

Before #189 we have observed in 2019 that UWB was not reliable enough to communicate the position between robots. So our robots ended up colliding into each other which made our game strategy fail. We have a few ideas related to power supply and heating issues that need investigation. By the end of this we should have a robust real-time communication of position between our robots.

@SyrianSpock SyrianSpock added this to the Summer 2019 milestone May 14, 2019
@SyrianSpock SyrianSpock added high-priority High priority, should be fixed ASAP needs-hardware-testing labels May 14, 2019
@antoinealb
Copy link
Member

For me this is actually two parts:

  1. We need boards that do not overheat and maintain a "reasonable" service. That means no overheating, no dieing when the bus voltage is a bit low, etc.
  2. We need a high level protocol to cope with packet loss. Since we now have a working IP over UWB implementation, we might use TCP for this directly (which is nice), or build something more complicated à la raft.

@SyrianSpock
Copy link
Member Author

Agreed, I think UWB boards' design could use a thorough review, and we can experiment with converting supply voltages on the board itself (using the +12V supply)

@antoinealb
Copy link
Member

Yes, I wanted to do a review using the newly found knowledge about heating. My guess would be somewhere on the power supply path something is bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high-priority High priority, should be fixed ASAP needs-hardware-testing
Projects
None yet
Development

No branches or pull requests

2 participants