Robot Interface

Different robots have different communication requirements for control and diagnostics. In ROS, this can mean different message types, different topic names, different interfaces for a robot in simulation versus reality, and so on. This can greatly complicate things as you end up having to create separate controllers and monitoring nodes for each platform. I created a robot interface abstraction layer to try to mitigate these issues. The idea is that each robot has its own interface that implements the requirements particular to that platform, and each interface inherits from a common interface. I have implemented a number of controllers in my controller package that use the common interface, such that the controllers are agnostic to the robot being controlled, and they can be instantiated with any interface in this package.

I have implemented interfaces for the KUKA LBR4+ (simulation), Baxter (real and simulation), and the Righthand Robotics ReFlex hand (simulation). Balakumar Sundaralingam has implemented an interface for the real and simulated Allegro hand.

Adam Conkey
Adam Conkey
Senior Software Engineer