[Blocked by DRIVE] Control Systems Drive Interface

[ntwong0]

Gazebo:

• twist commands working
• basic steering commands working
• velocity working

Next step: By 3/17

• add lidar in Gazebo
• interact with gmapping node By 3/24
• interact with ros_navigation node
• ros_navigation accepts NavGoal from rviz
• visualize the Rover moving from NavGoal -> Twist -> reaching destination

[ntwong0]

May 28 at 6:28 PM From @yosefmirsky Khalil's response to me asking about drive API: "Ima just hop in here. For the most part they communicate using XHRs, but the how and the what are no where near figured out. There has been little progress on the controls side. So no API or scheme/protocol exists. The drive system should be able to output status information like torque/current, speed, etc, but again, no work has been done."

May 28 at 6:27 PM Update from @yosefmirsky 's findings, drive subsystem team currently has no protocols for sending data to drive uC, so we are going to be blocked for a while.

May 23 at 12:34 PM Waiting on the rover, blocked by ControlSystems/Drive subsystems team

• how are commands sent to the Drive uC?
• how are statuses read from the Drive uC? @yosefmirsky harass the drive subsystem team

[ntwong0]

Blocked by #61