here are some correcitons I see:
when using go():
drone.go(Direction.RIGHT, 1, 30)
where your import section must also include: from CoDrone import Direction
(here is a the basic page for the go() command: https://support.robolink.com/codrone-library/go)
with regards to the set_pitch()/move() based on reading the code, it should work (though I've found that 30 and below sometimes has minimal effect, but not consistent)
@opencvfr3ak that is awesome! I too am trying to fine tune the codrone (but each pettern/code execution does not equate to a repeatable pattern) I've been trying to get a drone to take off (never the same twice) make a rectangle pattern and land (where it took off) and have been trying to get the camera to ID where it took off from. I'd be interested in looking at your code if you allow it to see where I've been screwing up. thnx for the heads up on the move() time savings, that should help as I experiment today. I too have seen inconsistencies with the Yaw.
Ive been trying to gauge with sensor is better, the X/Y of the gyro vs the optical. and both are showing inconsistent (different from each other) executions
Ultimately, (also new to drones) Id like
Awesome work, looking forward to seeing what else you are developing. Seeing what you post opens the doors of what I think is actually possible.
I have been coding my codrone with a raspberry pi 4 the past few days. something you have to do is look in your /dev folder:
ls /dev/tty*
it shoudl spit out a list of anything starting with "tty" and find the ttyUSB0 (in my case mine change on day 2 to ttyUSB1)
and also know what your codrone number is ad use this to connect to your codrone this is what I use:
// In Python
// Connection code to a specific CODRONE on Raspberry Pi
// where the number "8697" is the number to your CODRONE
// and the /dev/ttyUSB1 is the serial link used (not sure why they
// just didn't use the normal bluetooth
if not drone.connect("8697", "/dev/ttyUSB1"):
print("Failed to connect")
drone.close()
exit(4)
hope that helps.
As an aside: when coding python sometimes it will take 2-5 executions of the code before it finally connects. No clue why (either times out or says 0% battery, even with a fresh battery). it easily takes 20s for the connection to get established before the lights go solid green and liftoff.
or another method of better precision/tracking? from what I've been experimenting with it isn't as precise as I had hoped.
has anyone developed code to find a landing spot (by color/shape/pattern) for a drone when flying a pattern and sees their "landing spot" to self guide/land on it?
jsut an update, I was finally able to figure it out, updated the line to read for my specific USB and drone:
drone.connect(portName="/dev/ttyUSB0", deviceName="PETRONE 8697").
Next steps:
Robolink team!
I finally found your coveted openCV python files, and I have the openCV to capture the feed from the video wireless feed, BUT (and I have both the petrone and petrone-v2 libraries installed) but I get the error:
3.832] Could not find PETRONE
Using Ubuntu, PyCharm, and have had it working with your codrone library, but I think your petrone libriary appears more robust? or does your codrone library have all the functionality as the petrone (more? or less?) and I jsut need to recode the pythonn script to follow the codrone library?
Thnx for your help
I've been looking online but have not seen the tutorials for this. beside the currsory doc on install for pycharm.
[background] using ubuntu to code a CoDrone to start at a "helipad" fly over a 4'x8' table that has a HO gauge town and land back at helipad. wanting to use the FPV/openCV to ID the helipad (has a special pattern like QRcode maybe) and either follow a path on the town (like road) or stay over the board and not go over the edge, and once over the helipad when recognizing the pattern, land.
thnx