ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

jocaps's profile - activity

2012-08-23 18:03:50 -0500 answered a question Modeling URDF files using Blender and exporting to COLLADA format

Have you tried Blender 2.49b? You can still download it from their website.

Im not much into ROS but I am into Blender so I thought I give an answer too. Since after 2.49b Blender has rewritten it's API all anew. Which meant that all fan-made exporter/importer had to be rewritten as well. This resulted into some exporter/importer to be removed from the system or to be incomplete. Though I'd like to know why you want to use the .dae format? Is there a particular reason? You can also group and texture perfectly fine with .obj (Lightwave obj) and .mtl that comes with it. The format even supports curves and vertex grouping (not only object grouping like collada does) and it's more supported by other 3D softwares than collada is (even to this date when collada is becoming "trendy"). I do believe the latest version of Blender does fully support .obj format (at least with less bugs than the collada or wrl formats).

If you insist in using .dae and Blender 2.6x (or if ROS supports this much more than other 3D formats), then I would suggest that you convert the .dae into obj using the old blender 2.49b which might work, or using meshlab (but this is not also gauranteed as I also know that meshlab works and converts .obj and .mtl better than it does .wrl or .dae) and then try to open the .obj file in Blender 2.6x (if you insist in using Blender 2.6x).

Jose

2011-11-02 23:12:55 -0500 received badge  Famous Question (source)
2011-07-26 08:41:00 -0500 received badge  Notable Question (source)
2011-07-07 03:40:35 -0500 received badge  Nice Question (source)
2011-06-17 18:36:25 -0500 received badge  Popular Question (source)
2011-06-15 23:49:25 -0500 received badge  Scholar (source)
2011-06-15 23:49:17 -0500 received badge  Supporter (source)
2011-06-09 16:36:13 -0500 marked best answer Connecting two kinects with openni_camera will show only the first two topics that are read

The problem is USB bandwidth. A single USB bus can only handle two streams, as you've noticed. To get all four streams, you need each Kinect to be on a separate bus.

Most desktops these days have two Hi-speed USB (2.0) buses I think. You can check how many you have with something like lsusb | grep "2.0 root hub". lsusb will also show you which bus each Kinect is on. One Kinect yields three devices of type "Microsoft Corp.".

If you need another USB bus and have a PCI slot to spare, there are PCI cards that will give you that extra bus.

2011-05-25 11:25:55 -0500 received badge  Student (source)
2011-05-19 20:07:15 -0500 asked a question Connecting two kinects with openni_camera will show only the first two topics that are read

Hi,

I am having a little bit of a trouble trying to connect two kinect using openni and viewing them with rviz. I have this impression that this could be driver problem. Maybe someone more experienced could be kind enough to advise me. I have the following node connections: (oops my karma is not big enough to upload my rxgraph screenshot, I'll do it as soon as my karma reaches 20).

Basically two nodes are connected to rviz. The launch files are the following: test_2kinect.launch, test_frames1.launch, test_frames2.launch.

First I set rviz to have 4 cameras that gets camera1/rgb/image_color, camera2/rgb/image_color, camera1/depth/image_raw and camera1/depth/image_raw. I get usually 2 webcam images (rgb images). Naturally I want all 4 cameras to work. I did several experiments and apparently only 2 images are able to be displayed simulataneously like: depth from camera 1, image from camera 2 or depth from camera 1, image from camera 1, or depth from camera 1, depth from camera 2. Apparently the first two topics where rviz listens to will pass but the other ones that are connected wont get through. To do this, I just close any two cameras in rviz and set the other 2 open and then close the application and then kill the launch and restart rviz and the launch and I get the two images. Trying it with all 4 cameras open will display for me 2 rgb image. This is the reason why I suspect the driver. Even if I open another rviz process with different configuration the first rviz application that read the two topics will determine which two topics will give me images. This is totally weird. Anyone has any idea what's going on, or is it indeed the Primesense driver that is the devil?

Jose