Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Execution of trajectories #1

Closed
Makekihe opened this issue Nov 24, 2020 · 1 comment
Closed

Execution of trajectories #1

Makekihe opened this issue Nov 24, 2020 · 1 comment

Comments

@Makekihe
Copy link

Makekihe commented Nov 24, 2020

Hello mSimon,

We've talked previously on wilselby's GitHub (#46) with regards to performing 3D navigation of the Hector quadrotor in Moveit. I found it more suiting to continue the conversation here. I'm hoping that you can help me out if you have the time.

I've managed to compile both your and Tahsinkose's package on Kinetic (for whatever reason, this worked better than Melodic), and I've tried to understand the packages which you've used and developed.

  1. It seems like you both have created an action server (trajectory_action_pkg or hector_moveit_actions) and a secondary package for executing the trajectories which are developed in Moveit (quadrotor_control_system or hector_moveit_exploration). I'm interested in the go-to-goal/follow trajectory (with obstacle avoidance) functionality which it seems like you've developed inside your move_drone.py, yet I have no idea how to create this functionality myself. Are there any guides I can use to create similar packages?

  2. If I'm allowed to use your package (with your permission of cause), how can I incorporate it into my own workspace?

  3. I've tried to launch your package the way you've described here on your Github, however, RViz cannot open when using the roslaunch full_system_launcher system.launch command. It just remains at the loading window, as seen on the picture below. Note that Gazebo loads without problems. Furthermore, when using the rosrun quadrotor_control_system move_drone.py drone_name X Y Z THETA command, nothing happens (I assume this is because RViz refuses to load, but it could be something else). Do you know how to fix this?
    127089655_2492385384395267_8379033823060756314_n
    127242227_3755740141137783_5112371183088084441_n

@mSimon12
Copy link
Owner

mSimon12 commented Dec 2, 2020

Hi @Makekihe ,

Sorry for the delay.

  1. It seems like you both have created an action server (trajectory_action_pkg or hector_moveit_actions) and a secondary package for executing the trajectories which are developed in Moveit (quadrotor_control_system or hector_moveit_exploration). I'm interested in the go-to-goal/follow trajectory (with obstacle avoidance) functionality which it seems like you've developed inside your move_drone.py, yet I have no idea how to create this functionality myself. Are there any guides I can use to create similar packages?

The trajectory_action_pkg is the package where I have implemented the action responsible for calling moveit planning, to avoid collisions, and translate it into the motion execution.

  1. If I'm allowed to use your package (with your permission of cause), how can I incorporate it into my own workspace?

If you desire to apply the motion directly into a code implemented by you, the best option is to copy the code into the move_drone.py. It basicaly creates a client of the action that I have created and send the desired position.

  1. I've tried to launch your package the way you've described here on your Github, however, RViz cannot open when using the roslaunch full_system_launcher system.launch command. It just remains at the loading window, as seen on the picture below. Note that Gazebo loads without problems. Furthermore, when using the rosrun quadrotor_control_system move_drone.py drone_name X Y Z THETA command, nothing happens (I assume this is because RViz refuses to load, but it could be something else). Do you know how to fix this?

By default, my launch starts with the Gazebo paused. Have you started it?

*Rviz opens only after you start the Gazebo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants