You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that all the IMUs and FTs in the iCub and ergoCub robots we use have been migrated to multipleAnalogSensors interfaces, we can drop the use of IGenericSensor and IAnalogSensor in the YarpSensorBridge. Similarly to #911, we could take the occasion to just drop any custom remapping logic from YarpSensorBridge, and use use a multipleanalogsensorsremapper.
The text was updated successfully, but these errors were encountered:
traversaro
changed the title
YarpSensorBridge: Drop use of IGenericSensor and IAnalogSensor
YarpSensorBridge: Drop use of IGenericSensor and IAnalogSensor for reading sensors
Nov 15, 2024
I renamed the title as I realized that we are also using IGenericSensors to read the cartesian wrenches, and that info is not published by WBD with a usual chain of C++ device interface ---> NWS ---> NWC , so let's leave them aside for now. I wonder if we could just expose those using the existing https://www.yarp.it/v3.4/classyarp_1_1dev_1_1ISixAxisForceTorqueSensors.html inteface. If you think about it, in the end external wrenches estimates could be tought of virtual FT sensors, so that could make sense, but that is OT here.
Now that all the IMUs and FTs in the iCub and ergoCub robots we use have been migrated to multipleAnalogSensors interfaces, we can drop the use of IGenericSensor and IAnalogSensor in the YarpSensorBridge. Similarly to #911, we could take the occasion to just drop any custom remapping logic from YarpSensorBridge, and use use a
multipleanalogsensorsremapper
.The text was updated successfully, but these errors were encountered: