Icub-models

Latest version: v3.1.0

Safety actively analyzes 723296 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 5

2.2.1

Fixed

* Fix Gazebo Classic simulation of iCub 2.* and 3 models, that stopped working since the 2.1.0 release (https://github.com/robotology/icub-models-generator/pull/240). Note that this fix highlighted a bug in icub-models that was introduced in 1.26.0, namely that the names of the FT sensors in the iCub models is not consistent with the real robot. This issue will be fixed in a future release, see https://github.com/robotology/icub-models-generator/issues/242 for more details.

Changed

* Tune position PID gains for torso for iCub 2.* (https://github.com/robotology/icub-models-generator/pull/241).

2.2.0

**Due to an error, this release did not contained improvements.**

2.1.0

Changed

* For consistency with the robot, now iCub simulated models publish their Force-Torque Sensors measurements via the [`multipleanalogsensorsserver`](https://www.yarp.it/latest//classMultipleAnalogSensorsServer.html) YARP device (https://github.com/robotology/icub-models/issues/198, https://github.com/robotology/icub-models-generator/pull/239, https://github.com/robotology/robots-configuration/pull/517). The `name` parameter passed to this device is: `/<robotPortPrefix>/<partName>/FT`. This means that for each part there will be a `multipleanalogsensorsserver` device that will open the following YARP ports (these YARP ports are not meant to be accessed directly, but should be accessed instead via the [`multipleanalogsensorsclient`](https://www.yarp.it/git-master/classMultipleAnalogSensorsClient.html) device):
* `/<robotPortPrefix>/<partName>/FT/measures:o` : that publishes sensors information for the part, using the structure defined in https://github.com/robotology/yarp/blob/master/src/devices/multipleAnalogSensorsMsgs/multipleAnalogSensorsSerializations.thrift
* `/<robotPortPrefix>/<partName>/FT/rpc:o` : that expose several information related to the part via a YARP RPC port

2.0.1

Fixed

* Harmonize iCubGazeboV2_5_visuomanip RGB cameras port names (https://github.com/robotology/icub-models/pull/196).

2.0.0

Fixed

* Make models compatible with the YARP 3.8 (https://github.com/robotology/icub-models/issues/171, https://github.com/robotology/icub-models/pull/188, https://github.com/robotology/icub-models-generator/pull/231).
* Fix incompatibility between RViz2 and iCubGazeboV3 model ( https://github.com/robotology/icub-models-generator/issues/229 ).
* Uniform IMUs sensor names (https://github.com/robotology/icub-models-generator/pull/235).
* Add partial support to expose sensor data of iCubGazeboV3 on ROS2 (https://github.com/robotology/icub-models-generator/pull/228).

1.26.0

Changed
* Export frames in urdf for the sensors (imu and Ft sensors) (https://github.com/robotology/icub-models-generator/pull/227).
* Migrate iCub3 models to use gazebo_yarp_robotinterface plugin (https://github.com/robotology/icub-models-generator/pull/222).

Fixed
* Fix finding the `iCub` package in ROS2 (https://github.com/robotology/icub-models/pull/178).

Page 2 of 5

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.