IMU impemented as analogDevice about gazebo-yarp-plugins HOT 5 CLOSED

Note:
The module 3DM_GX3 can be used as a reference. It is the device used to read data from the real IMU sensor on coman.
The moudle is in iCub/main/src/libraries/icubmod/imu3dm_gx3

the IGenericSensor interface has to be implemented and the appropriate wrapper to use is the ServerInertial, which is into yarp/libYARP_dev/include/yarp/dev/ServerInertial.h

from gazebo-yarp-plugins.

I am trying to tackle this issue, but apparently there is no way to obtain the parent ModelPtr from the SensorPtr provided as an argument of the Sensor Plugin (at least I was not able to find a way: http://gazebosim.org/api/2.0.0/classgazebo_1_1sensors_1_1Sensor.html ). So it is not possible to use directly the singleton handler.

Do you think it could make sense to extend the handler to handle also sensor pointers (by using as a key the scoped name of the sensor, to avoid name clashes between robots with sensor with the same name)?
This could potentially mean a lot more values in the handler, but as long as the handler is used only in initialization I don't think this would be a big issue.

from gazebo-yarp-plugins.

I add a little clarification because I am afraid I was not clear: my idea is to use the runtime scoped name of the sensor (obtained by GetScopedName()) as a key for the handler, and to pass this key to the driver by adding it at runtime to the properties that are passed to the driver, without any sensor name/key hardcoded in the configuration files.

from gazebo-yarp-plugins.

I have implemented the proposed solution in commit d53d8ea of development branch. I am not really sure about the solution of using the ScopedName of the sensor as the key for the singleton because I find (but It can be a wrong assumption on my side) that the traditional spirit of yarp device configuration file is that everything needed to create a device (possibly using also yarpdev utility) is found in the relative .ini file.
On the other hand I think every gazebo yarp device will always be created explicitly by the relative gazebo yarp plugin (correct me if I am wrong) so having an "incomplete" configuration file is not an issue.

from gazebo-yarp-plugins.

Done in a31320c

from gazebo-yarp-plugins.