Two sensors connected to the jetson/raspberry pi, when time is not crucial. [closed]

asked 2020-02-06 06:58:39 -0500

femust gravatar image

Hey,

I have the following case which I am not sure how to solve:

I have two Asus xtion pro and Jetson Nano. Jetson Nano is able to stream only one asux xtion pro at a time.

So my solution currently is to use ros::topic::waitforTransport when I need to get data from one point cloud wait some time (let's say 0.5s) and get a point cloud from the other sensor (time robustness it's not important in this application).

So If I want a typical XYZ point cloud everything works nice. On the other hand when I want XYZRGB cloud then it's also fine in terms of XYZ but with color is a problem, because it's blurry-whity.

I did some tests, and it seems that the reason is auto-exposure, since when I open in rviz, there is a kind of flash at the beginning and then it's fine. Because of this flash, the point cloud is whity despite the real color. When I am using only one camera and I am saving data there is RGBXYZ normally (when I'm streaming all the time point clouds). So it seems that the problem is with the "waitforTransport" since it seems it asks asus to turn on. Then asus sends data back, but in the meantime asus wants to do auto-exposure - for this reason the point cloud is either not properly colored or blurry-white (more frequently). So the question is what should i do in this case?

In general application is that I have a rotating frame, two Asus and i want to catch point cloud with color and then icp-ed them together.

Thanks for suggestions.

edit retag flag offensive reopen merge delete

Closed for the following reason duplicate question by stevemacenski
close date 2020-02-06 12:46:25.604147

Comments

Please ask your question only once. I'm leaving the other one open since the title was better (with the same body of text).

stevemacenski gravatar image stevemacenski  ( 2020-02-06 12:46:46 -0500 )edit

yes, sorry i'm not sure how i did that :)

femust gravatar image femust  ( 2020-02-06 14:06:06 -0500 )edit