Skip to content
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

imu sensor description #69

Closed
guihomework opened this issue Feb 3, 2020 · 3 comments
Closed

imu sensor description #69

guihomework opened this issue Feb 3, 2020 · 3 comments

Comments

@guihomework
Copy link
Contributor

Dear Shadow,
in this commit df674fe an imu description was added to the URDF, following the sensor description of URDF, probably this one https://wiki.ros.org/urdf/XML/sensor which is no really "supported". Do you use your own parser ?

however, sensor parsing in URDF is broken for ages now, and we maintain a PR that fixes it (but it still did not get merged) following some newer way (more advanced, to support more types of sensors). see ros/urdf#5 and ros/urdfdom#84
that follows this sensor description proposal https://wiki.ros.org/urdf/XML/sensor/proposals in which "type" is a required field .

At our side your addition now obviously fails to parse, because the type is missing.

[ERROR] No child element defining the sensor.

Would it be harmful to add this field (I can provide a PR) so that your description becomes compatible with this new URDF parser we suggest (hence supporting us in that quest). It will help describe the sensor better.

@beatrizleon
Copy link
Contributor

Hi @guihomework , yes please send us the pr

@guihomework
Copy link
Contributor Author

Hi,
well, it seems one needs not a tag but a child element. An ideal child element could be <imu /> but the current xacro (melodic) complains that the imu element is interpreted for now as a call to the xacro:imu macro...
There are two ways to solve our problem in the sensor parser:

  1. add a child element called <unknown_type /> for the moment, but this is not helpful as it does not add any value to the description of the sensor in urdf
  2. rename the xacro macro imu to imu_sensor for instance, and then use the child element.

Overall, how is this sensor description used ? is it detected my name in your own parser somewhere ? There is already a link imu and an associated joint which probably is what you need to get TF transforms from palm to IMU, so what is the sensor tag useful for ?
I don't want to make you solve our problems if this is not going to be useful in the future somehow

@guihomework
Copy link
Contributor Author

#72 is the solution 2)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants