messages not published at all

[gitunit]

i've compiled the yellowstone branch successfully and the app starts.
however messages never get published, rqt_topic shows the topics but bandwidth and Hz says "unknown".
also i realized that the callback in the ImagePublisher is never called.
though i saw once some debugging stuff in the logcat but that happened only once and still there were no messages published. currently i would only need raw images, preferably fisheye.
do you know what could be the issue here?

[carlosjoan91]

Color images are a work in progress and they are not being published in the
current version. However, are you not getting any messages published at all
(I.e. depth and pose)? If so, any exceptions while that happens? Are you
placing the tango library in the specified folder?
On Jan 6, 2016 12:59 PM, "gitunit" notifications@github.com wrote:

i've compiled the yellowstone branch successfully and the app starts.
however messages never get published, rqt_topic shows the topics but
bandwidth and Hz says "unknown".
also i realized that the callback in the ImagePublisher is never called.
though i saw once some debugging stuff in the logcat but that happened
only once and still there were no messages published. currently i would
only need raw images, preferably fisheye.
do you know what could be the issue here?

—
Reply to this email directly or view it on GitHub
#5.

[gitunit]

yes, no messages arrive. i placed everything as instructed. the header file i put first into the specified folder with a subfolder "include" but that didn't compile so i put both files into the folder without the "include" subfolder and then it compiled.

[carlosjoan91]

Do you get any exceptions on android studio?

2016-01-06 16:35 GMT-06:00 gitunit notifications@github.com:

yes, no messages arrive. i placed everything as instructed. the header
file i put first into the specified folder with a subfolder "include" but
that didn't compile so i put both files into the folder without the
"include" subfolder and then it compiled.

—
Reply to this email directly or view it on GitHub
#5 (comment)
.

[gitunit]

seldom but these are resolved after the usual reboot

[gitunit]

i restarted the application again and now it seems to do stuff due to logcat. though still no ROS messages.
seeing debug strings with TAG "log-per-line" and "st-log"

above is the following, could be relevant:

01-07 00:10:53.827 188-677/? E/tango: calibration-provider.cc:180 Online calibration file provided, but does not exist: /sdcard/config/online-calibration.xml. Reverting to factory calibration.
01-07 00:10:53.828 188-677/? I/tango: tango-hal-device-wrapper.cc:61 Failed to open libtango_hal.so: dlopen failed: library "libtango_hal.so" not found
01-07 00:10:53.828 188-677/? E/tango: tango-hal-sensor-graph.cc:85 Could not open device shared library!
01-07 00:10:53.828 188-677/? I/tango: application-base.cc:104 Using sensor graph.
01-07 00:10:53.828 188-677/? I/tango: ocv-freak-feature-tracker.cc:57 Max keypoints which will be sent for descriptor extraction after pruning: 800
01-07 00:10:53.828 188-677/? I/tango: ocv-freak-feature-tracker.cc:62 Number of stages in which frame-frame matching will be run: 2
01-07 00:10:53.828 188-677/? W/tango: gpu-dog-pyramid.cc:104 CUDA has an error prior to starting module: invalid argument
01-07 00:10:53.828 188-677/? I/tango: ocv-freak-feature-tracker.cc:57 Max keypoints which will be sent for descriptor extraction after pruning: 800
01-07 00:10:53.828 188-677/? I/tango: ocv-freak-feature-tracker.cc:62 Number of stages in which frame-frame matching will be run: 2
01-07 00:10:53.829 188-677/? I/tango: native-sensors.cc:84 Have calibrated gyro
01-07 00:10:53.831 171-1013/? I/Camera2ClientBase: Camera 0: Opened
01-07 00:10:53.832 171-1013/? I/ProCamera2Client: ProCamera 0: Opened

[carlosjoan91]

Seems it's a problem with the tango library loading, does the version you
placed in the folder match the version your tango (And Project Tango Core
app) is at? Can you run other project Tango apps? (The last tested version
is Zeno, but I see nothing on the release notes that would imply more
recent versions would break it).

2016-01-06 17:17 GMT-06:00 gitunit notifications@github.com:

i restarted the application again and now it seems to do stuff due to
logcat.
seeing debug strings with TAG "log-per-line" and "st-log"

above is the following, could be relevant:

01-07 00:10:53.827 188-677/? E/tango: calibration-provider.cc:180 Online calibration file provided, but does not exist: /sdcard/config/online-calibration.xml. Reverting to factory calibration.
01-07 00:10:53.828 188-677/? I/tango: tango-hal-device-wrapper.cc:61 Failed to open libtango_hal.so: dlopen failed: library "libtango_hal.so" not found
01-07 00:10:53.828 188-677/? E/tango: tango-hal-sensor-graph.cc:85 Could not open device shared library!
01-07 00:10:53.828 188-677/? I/tango: application-base.cc:104 Using sensor graph.
01-07 00:10:53.828 188-677/? I/tango: ocv-freak-feature-tracker.cc:57 Max keypoints which will be sent for descriptor extraction after pruning: 800
01-07 00:10:53.828 188-677/? I/tango: ocv-freak-feature-tracker.cc:62 Number of stages in which frame-frame matching will be run: 2
01-07 00:10:53.828 188-677/? W/tango: gpu-dog-pyramid.cc:104 CUDA has an error prior to starting module: invalid argument
01-07 00:10:53.828 188-677/? I/tango: ocv-freak-feature-tracker.cc:57 Max keypoints which will be sent for descriptor extraction after pruning: 800
01-07 00:10:53.828 188-677/? I/tango: ocv-freak-feature-tracker.cc:62 Number of stages in which frame-frame matching will be run: 2
01-07 00:10:53.829 188-677/? I/tango: native-sensors.cc:84 Have calibrated gyro
01-07 00:10:53.831 171-1013/? I/Camera2ClientBase: Camera 0: Opened
01-07 00:10:53.832 171-1013/? I/ProCamera2Client: ProCamera 0: Opened

—
Reply to this email directly or view it on GitHub
#5 (comment)
.

[gitunit]

i use the latest version capella and all tango apps work. tango core is also latest and should match.

[carlosjoan91]

I would need to test it myself with the latest version in that case, but I
don't have access to the tablet for around 2 weeks. In the meantime other
issues I can think of is general ROS troubleshooting. (e.g. times being
synchronized, having a good network connection to master, etc.).

2016-01-06 17:41 GMT-06:00 gitunit notifications@github.com:

i use the latest version capella and all tango apps work. tango core is
also latest and should match.

—
Reply to this email directly or view it on GitHub
#5 (comment)
.

[gitunit]

ok, i see. ROS in general works for me as i've other applications running flawlessly. maybe i can try using the capella support library files. edit: with the support library files it's the same, no ROS messages.

[carlosjoan91]

Just tested in the tablet, with it updated to the latest OTA, latest project tango core, and latest C API extracted in the folder, and I get both odometry and depth running. This is a newer release (Electra), released after the last time we spoke. Can you try with this one and let me know how it goes?

[gitunit]

still nothing. topics are advertised but never actually published. 😞

[nuclearmistake]

Smells like DNS. Try export ROS_HOSTNAME="IP address" in the subscriber's shell before running it... With the IP of the machine running the subscriber on the right hand of the assignment.

If the tango cannot figure out the IP of the subscriber to open the TCP transport, it won't establish the connection.

[gitunit]

tried that, nothing changed except now i see some log messages about features ..but nothing inside rviz or rqt_topic. the ROS_HOSTNAME should just contain the ip without the port of the pc right?

[carlosjoan91]

Yes, ROS_HOSTNAME should be the ip without the port, also make sure you
have set your ROS_MASTER_URI to the actual machine IP, and not to
localhost.

2016-01-25 18:44 GMT-05:00 gitunit notifications@github.com:

tried that, nothing changed except now i see some log messages about
features ..but nothing inside rviz or rqt_topic. the ROS_HOSTNAME should
just contain the ip without the port of the pc right?

—
Reply to this email directly or view it on GitHub
#5 (comment)
.

[nuclearmistake]

What does rqt_graph show?