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

Update simulator.py #13

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dullahgtt
Copy link

From he looks of it, just changing the library to the better djitellopy library, the simulator still works perfectly. Please let me know if it does not work.

From he looks of it, just changing the library to the better djitellopy library, the simulator still works perfectly. Please let me know if it does not work.
Copy link
Contributor

@azbones azbones left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I just tested your branch with my drone and everything seemed to work fine. Can you also please update the setup.py settings so that the install now includes the new library? You can update the version in that file from 0.0.1 to 0.0.2. After we merge your contributions, I can update the README to reflect the change in the library and also thank you for bringing it up and making a contribution. @sean-schaefer I looked through the new lib and didn't see anything that looked like it wouldn't work with our existing command sets, but you might double check.

Thanks for taking the initiative and making a contribution!!!!

@sean-schaefer
Copy link
Contributor

Hey @dullahgtt, thanks for your effort here. I went through some testing with my drone and I think we'll need to make a few more changes as the API for djitellopy is a little bit different.

Currently when we deploy the drone, we call the send_command function from easy tello, which waits for a response from the drone. That function doesn't exist in djitellopy, but they do have two similar functions: send_command_with_return and send_command_without_return. I haven't dug too deep yet but it's possible we could drop-in replace with the "with return" function, though I would probably want to review the whole API and confirm if there's not any better integration points.

If you have the bandwidth to look into those additional changes, that would be much appreciated, but I can also investigate further when I get some more free time, probably in a week or so. Thanks again!

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

Successfully merging this pull request may close these issues.

None yet

3 participants