Cedric,
Awesome! Where do you think the CPU load is coming from? Can you profile it? Let's see if there's ways of improving
that, as clearly we wont have too many CPU cycles left for processing if the driver alone is eating up that much :)
Are you using the ros-pkg-git kinect driver?
Cheers,
Radu.
On 11/18/2010 07:48 AM, Cedric Pradalier wrote:
>
>
> For information, we just managed to have the kinect working on a gumstix
> overo (arm). Once the cross-compiling is done, there is no major
> impediment.
> We temporarily hacked the driver to publish only the depth image for
> this test.
>
> In this setup, we publish about 9 fps (rostopic hz) and use around 65%
> of the CPU.
>
> Next step: see if we can even control a robot with this information :)
>
> Cheers
>
(text/plain)