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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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)
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.
The text was updated successfully, but these errors were encountered: