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

Empty mesh extracted #385

Open
jmreyesgarcia opened this issue Feb 8, 2018 · 5 comments
Open

Empty mesh extracted #385

jmreyesgarcia opened this issue Feb 8, 2018 · 5 comments

Comments

@jmreyesgarcia
Copy link

jmreyesgarcia commented Feb 8, 2018

Hi. First things first: thank you for this wonderful app, It is being very helpful for me in in order to accomplish 3d mapping tasks mounted in a small vehicle. The question is I would like to add some feedback while recording data and for that purpose I would like to enable 3d mesh reconstruction in rviz. But I'm finding unable to show the mesh markers.
I got two devices: Zenfone AR and Lenovo Phab 2 Pro, and in them both and updated to last Tango version.
I'm loading rviz config and I can see everything except for mesh (example with Zenfone AR):

captura de pantalla de 2018-02-08 12-52-24

I checked rostopics and from time to time I receive data from /tango/reconstruction/mesh and /tango/reconstruction/mesh_marker

Later I wen to adb debug for checking the device output while scanning, and I got this:

02-08 12:17:29.555 22784-23395/? I/native: tango_3d_reconstruction_helper.cpp:180 Empty mesh extracted.
02-08 12:17:29.930 22784-23395/? I/native: tango_ros_node.cpp:1150 Empty mesh array!

Any clue what I'm doing wrong? I checked ros parameters and seem to be fine. Also I'm using usb thetering for avoiding wifi delay. Enable depth camera and color camera are on (except for Lenovo Phab 2 Pro that color camera can't be enabled because Android version)

@PerrineAguiar
Copy link

Hi @metai, thanks for the kind words.

I could not reproduce your issue with a Lenovo Phab 2 Pro.
You can double check that the related rosparams are set correctly:

$ rosparam get /tango/enable_depth 
true
$ rosparam get /tango/enable_color_camera 
true
$ rosparam get /tango/enable_3dr_mesh 
true

One side note, on the Lenovo Phab 2 Pro the color camera is enabled by default, and can not be disable due to Android version (I agree it is not very clear in the app). So you should receive a color image.
Then if depth and 3dr_mesh are also enabled, you should received meshes on /tango/reconstruction/mesh.

According to the device output, the params are set correctly but the meshes extracted by Tango are all empty (see here), so in the end the marker array is empty (see here). I can't really understand why. It usually happens that some extracted meshes are empty, but not all.

Some links to the Tango3DReconstruction API that could be useful while investing this:

@jmreyesgarcia
Copy link
Author

jmreyesgarcia commented Feb 14, 2018

Hi @PerrineAguiar;
Thank you very much for your response! Indeed this world of indoor positioning and robotics is starting to engage me a lot thanks to your app.
Could we try to discard software versions firsts?
I'm using, in Lenovo Phab 2 Pro:

  • Tango Ros Streamer from Play Store v1.3.1
  • Ubuntu 16.04
  • Ros lunar (also tried ros kinetic with same results) from
    sudo apt-get install ros-lunar-desktop-full
  • Tango core m20
  • Server parameters are true, the three of them
  • Create new localization map enabled or disabled (both same results)
  • Rviz config file is the one from github and Rviz version is 1.12.15

Anything different?

@PerrineAguiar
Copy link

Here are what differs for me:

  • Ubuntu 14.04
  • ROS Indigo
  • Rviz version 1.11.18

@jmreyesgarcia
Copy link
Author

jmreyesgarcia commented Mar 2, 2018

Dear @PerrineAguiar;

I tried Indigo in Ubuntu 14.04 and everything is working! I have to do more test in order to reach a conclusion, but it seems that in kinetic mesh messages are not working, maybe due to ros message differences in the distribution?
Thank you for your support,

Regards

@PerrineAguiar
Copy link

@metai Good news!
I am not aware of changes in the message definition of MarkerArray.
If you find the root cause of the problem, please add a comment to this issue.
Thanks

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