List view
Updating to newer motor libraries written in C++, Adding imu feedback to the omnibot project with FreeRTOS
Overdue by 6 year(s)•Due by April 30, 2019- Unified way of reporting errors, with consistent error codes - Recover from non-fatal errors (e.g. reset automatically if necessary) - Failsafe in case error reporting/recovery fails, e.g. watchdog timer - Way of logging MCU operations. There may be dedicated functionality in the MCU chip that does this. - Store the logs and/or expose to the output or debug UART live, to aid in debugging
No due dateThis milestone will be met by the following: - Decide on command structure to the MCU (#97) - Decide on structure of output from the MCU for the PC to parse - Implement parsing/serialization of the command/output structures on MCU and PC side - Unify command and output format between MCU and PC (one source of truth) - Implement sugar for writing a human-readable command and mapping it to the bytes sent to the MCU. This would allow for writing test scripts with a shell-like format (e.g. `soccerbot-cmd get --forced imu motor`) to be used in CI runtime tests. Similarly, sugar for MCU output would make tests more readable when checking for expected output.
No due date•0/1 issues closedThe goal is to have transmission and reception streams between the PC and microcontroller that operate independently of each other. This will enable new modes of operation, such as streaming data from the microcontroller at fixed frequencies or on demand, while at the same time being able to send it commands to change its behaviour.
Overdue by 6 year(s)•Due by April 30, 2019-Be able to communicate with slave devices via I2C -Send command to GLCD and display IP address
Overdue by 6 year(s)•Due by April 30, 2019-All projects separated from Eclipse and should be built independently through a makefile system that can be extended easily (future-proof) and is developer-friendly -Automate builds (CI) -Automate testing on builds (CI)
Overdue by 6 year(s)•Due by May 3, 2019•5/8 issues closed