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

Behavior simulated drones is different from real drones #9

Open
hc825b opened this issue Aug 6, 2019 · 1 comment
Open

Behavior simulated drones is different from real drones #9

hc825b opened this issue Aug 6, 2019 · 1 comment
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@hc825b
Copy link
Member

hc825b commented Aug 6, 2019

Currently in either cymulator/Drone/goto.py or cym_deivce/cym_waypoint_driver_drone.py

  1. the drone periodically publishes reached topic instead of only publishing when reached a waypoint.
  2. The drone goes to a waypoint without considering the frame id.

The drone should only publishes to reached in following conditions:

  • True: the drone has reached the waypoint.
  • False: it is impossible for the drone to reach the waypoint.

The desired way to handle waypoint topic is:

  • With frame_id=0, queue the waypoint message
  • With frame_id=1, pop and store all previously queued messages as a path and move accordingly
@hc825b hc825b added bug Something isn't working help wanted Extra attention is needed labels Aug 6, 2019
@hc825b
Copy link
Member Author

hc825b commented Aug 24, 2019

In ac951fc, reached topic is published only when the drone reach current waypoint.

Still need to handle frame_id

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant