Silvio Traversaro
Silvio Traversaro
In ergocub, there is sometimes the need to include some devices in the `gazebo_yarp_robotinterface` that can be enabled or disabled by the specific user. The main use cases is to...
Since when gazebo-yarp-plugins was created, the YARP's torque control model (see http://wiki.icub.org/wiki/File:ICub_Control_Modes_1_1.pdf) has been implemented in `gazebo_yarp_controlboard` by passing directly the reference torque to the `Joint::SetForce` method of Gazebo. However,...
Probably we need something similar to https://github.com/robotology/gazebo-yarp-plugins/compare/master...morpheus1820:gazebo-yarp-plugins:gpu_ray , but with a way to support both ray and gpu_ray in the same codebase (we can just use the result of the...
gazebo-yarp-plugins 5 in particular: * will drop the support for implicit wrappers * will remove the plugins that are not useful anymore as they were made superfluos by the robotinterface...
https://github.com/robotology/gazebo-yarp-plugins/pull/532 added a `gazebo_yarp_robotinterface`. However, for YARP devices to be available to be connected to yarp device instantiated by the robotinterface plugin, it is necessary that the plugin support specifying...
It is not necessary since we now have `gazebo_yarp_robotinterface`, from which we can instantiate `fakeMotionControl` device from YARP directly.
Since the beginning of `gazebo-yarp-plugins`, the general pattern of each plugin that exposed a given Gazebo functionality in YARP (at least the one that exposed functionalities available on real robots,...
The tests added in https://github.com/robotology/gazebo-yarp-plugins/pull/529 are segfaulting on macOS with Gazebo installed via Homebrew.
See https://github.com/robotology/gazebo-yarp-plugins/pull/566#issuecomment-888971686 .