-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose information provided by embObjMAIS YARP device using a non-deprecated interface #851
Comments
Regarding the cc @randaz81 |
We will need to address this task as per robotology/yarp#2999 (comment). |
/remind August 28 |
⏰ Reminder |
Work started: I will test it on |
Today I successfully tested these changes on <device xmlns:xi="[http://www.w3.org/2001/XInclude"](http://www.w3.org/2001/XInclude%22) name="left_arm-MAS_wrapper" type="multipleanalogsensorsserver">
<param name="period"> 10 </param>
<param name="name"> /icub/left_hand/MAIS </param>
<action phase="startup" level="5" type="attach">
<paramlist name="networks">
<elem name="leftMais"> left_arm-eb26-j12_15-mais </elem>
</paramlist>
</action>
<action phase="shutdown" level="5" type="detach" />
</device> Here is the
and here is the output:
Finally, I discovered and fixed a bug on how the timestamp was set, see |
Great! |
Is your feature request related to a problem?
I noticed that the
embObjMAIS
device is currently exposing its information via theIAnalogSensor
YARP interface, that anyhow has been deprecated (see https://www.yarp.it/latest/group__dev__impl__deprecated.html).Probably we could consider to expose the info via either:
yarp::dev::IEncoderArrays
: interface that is part of the multiple analog sensor interfaces, however has the downside that you cannot expose a name for each encoderyarp::dev::IAxisInfo
andyarp::dev::IEncoders
these interfaces are the same used to expose "regular" joint encoders, but I am not sure that thenws
andnwc
work fine if one implements only these interfaces and not all the rest of control-related interfaces.The solution you would like to have available
See feature description.
Alternatives you have considered
See feature description.
Additional context
I realized this while thinking about https://github.com/orgs/robotology/discussions/609 .
The text was updated successfully, but these errors were encountered: