Replies: 2 comments 1 reply
-
|
If anyone is having problems with the release 2023.05.0 to read FT sensors on real iCub, please note that we discovered a bug related to that that is being fixed by robotology/icub-main#892 . |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
2023.05.0 Distro Announcement
Brief description of the announcement
Hello @robotology/everyone 👋
The iCub project is happy to announce our Software Distro 2023.05.0 📦
This is a major release that comprises binary packages as well. Therefore, follow the instructions available in our documentation to upgrade your system and/or download the new dependencies.
You can find the tags composing this distro in our Software Versioning Table.
Detailed context
This distro is shipped with several updates and fixes, including the ones listed hereafter:
🆕 Updates
🔘
embObjFTSensorreplacesembObjStrainembObjFTSensornow handles alsostrainboard, this madeembObjStraindevice obsolete, then it has been removed.embObjFTSensorhandle strain board for removingembObjStraindevice icub-main#873🔘 Refactored how FT sensors data is published
This Distro ship a deep refactor on how the FT sensors data is published both on real and simulated robots. Now both simulated and real robot publish their Force-Torque Sensors measurements only via the
multipleanalogsensorsserverYARP device. Thenameparameter passed to this device is:/<robotPortPrefix>/<partName>/FT. This means that for each part there will be amultipleanalogsensorsserverdevice that will open the following YARP ports:/<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 portThese YARP ports are not meant to be accessed directly, but should be accessed instead via the
multipleanalogsensorsclientdevice.The publishing via
AnalogServerhas been removed since this Distro.Here some development:
analogServerwithmultipleanalogsensorsserverfor publishing FT data – Stint 1 robots-configuration#470analogServerwithmultipleanalogsensorsserverfor publishing FT data – Stint 2 robots-configuration#485🔘 Fixed launching face expressions on iCub
We fixed the face expressions, which now rely on the use of
serialPort_nws_yarpthrough the following PR's:serialporttoserialPort_nws_yarpicub-main#877🔘 Introduced
robots-configurationCI dry-runThis is the first distro sporting the CI dry-run of the robot configuration files.
The goal is to check the consistency of XML files (e.g., missing files, malformed syntax...) as well as of the device drivers launched with the robot (e.g., missing parameters, deprecated syntax...) within the CI of the
robots-configurationrepository for each proposed changes through PR's.This way, we can easily detect errors and leftovers ahead of the deployment.
The outcome of the dry-run is returned as an artifact within the CI workflow.
🔘 Calibration 14
This Distro provides the new calibration 14: it has been developed for calibrating the joint with the absolute encoder at the joint (which currently works with POS service / FAP encoder sensor) and with incremental encoder at the motor. The calibration 14 is useful to calibrate the incremental encoder reaching a hardware stop and thus ensure that the movement of the rotor is always within the limits specified by the user, avoiding damage to the motor itself.
👴 Deprecations
🔘 Deb binaries
As discussed here, we decided to deprecate the apt binaries in favor of conda ones that are delivered for both Linux, Windows and macOS.
Please refer to the official documentation for further details.
Beta Was this translation helpful? Give feedback.
All reactions