looks like some bugs about moving the virtual camera (TF and joint_states)

[danqu130]

After start the bebop_nodelet.launch, use rqt_tf_tree tool, seems work fine.
use rostopic echo /bebop/joint_states seems get the correct camera Pan&Tilt states.
and I try to move the virtual camera, for example,

rostopic pub /bebop/camera_control geometry_msgs/Twist "linear:
  x: 0.0
  y: 0.0
  z: 0.0
angular:
  x: 0.0
  y: -10.0
  z: 0.0"

The camera view is moving, but use rostopic echo /bebop/joint_states can't get any messages any more, and rqt_tf_tree tools shows bellow,

It seems that the connection is interrupted.
How to fix it?

Thanks!

[danqu130]

I have tried indigo-devel and sdk-3-12 two branches of this package, it seems that this problem still exist.

[Ignacio1994]

I have the same problem. Would you fix it? Is any other topic where I can get the camera angles?
Thank you.

[itssme]

I forked the repository and fixed the bug for the beobp2: https://github.com/itssme/bebop_autonomy

[gsilano]

@itssme, great!! Why you didn't open a pull request? It would be nice to share your results with others.

[itssme]

@gsilano Because I am not sure if the package would still work with the bebop 1. I only have a bebop2 to test :/

[gsilano]

@itssme, don't worry. I think the maintainer or contributors have a Bebop 1 to test the code.

[itssme]

@gsilano Ok, I made the pull request: #178

[LArayane]

@itssme @gsilano why it is called virtual since there is a camera there!!! I don't get it

[gsilano]

Hi @LArayane , I really don't know. You should ask the authors of the ROS package. However, please, ask your questions in the relevant sections. If there are no issues on this feel free to open a new one, otherwise follow the existing discussions.