Tyler Gamvrelis
Tyler Gamvrelis
# Purpose This issue is where we can track all our ideas for what we want to improve after Dec. 1. They can be anything, from _tiny_ things that irk...
**Describe the feature** Since we have made good progress on Ethernet integration and will have the PC interface smoke test done relatively soon, now is a good time to start...
**Describe the feature** Unite the omnibot with the code in /Common. **Reason for request** Issues such as #187 motivate the idea that the omnibot should depend on the same code...
**Describe the feature** The omnibot should return IMU data. **Reason for request** The controls and software teams would like the omnibot's telemetry to be as close as possible to that...
**Describe the feature** Automate the task of making sure code is styled consistently. **Reason for request** Despite people's best intentions and the fact that we have a coding style, it...
**Describe the feature** The IMU driver code makes calls to HAL and FreeRTOS functions directly. This means we cannot easily unit test this code. This feature will be implemented when...
**Description** Presently, the `UartDriver` class provides synchronization with interrupts (i.e. it will block a thread until the callback function is executed or the transfer times out), but does not provide...
# Purpose We can use this issue to track tutorials that we want to make # Items - [ ] C++ project setup in System Workbench - [ ] FreeRTOS...
**Describe the feature** Controlling motors via specification of velocity **Reason for request** RL team uses velocity control in their models. Thus, future iterations of the control systems may require velocity...
The Dynamixel motors use a half-duplex UART for communication, therefore there is no reason we need to use full-duplex UARTs to communicate with them. In fact, this only complicates the...