Created by [ Avery Chiu], last modified on Jan 08, 2021
Verify the newly designed CAN interface works under all possible conditions and scenarios
Perform preliminary tests with the CAN interface to make sure code can be compiled on rugged. Check to make sure any dependencies are not missing for ROS, CAN tools, etc.
Ensure that the interface is able to read messages from path-planning correctly. Next, verify the interface is able to encode the messages correctly so the CAN bus can understand what commands to send.
From the competition video at the software onboarding event, we need to make sure that the car safely stops in the case we cannot perform a task autonomously. Confirm we have a procedure that is able to stop the vehicle in any emergency scenarios.
Do rigorous testing with the car functioning in autonomous mode. Tests should include all the competition challenges and failure modes.
Need to ensure that data can be sent properly to the data monitoring stack.
Set up the pipeline to move data from the CAN bus to the data monitoring stack
Tables and metrics can be set up with the data monitoring stack, currently, everything is downloaded but it must be prepared so that it is ready to receive data from the CAN bus and log it properly
With help from infrastructure, add the CAN and Telemetry repos to the WATO mono repo.
Coordinate with infrastructure on how to add the repos with all the dependencies we have for CAN and telemetry. This includes our custom messages for CAN and any DBC files.
Figure out how to dockerize CAN. The CAN buses use serial protocol so the docker images need to be able to access the required ports and route the data accordingly.
Figure out how to dockerize blue light. Blue light uses USB so the docker images need to be able to access the required ports and route the data accordingly.
Document generated by Confluence on Nov 28, 2021 22:40