@johnnycurry Hello it appears that the remote may not have been in upload mode. Please check out this video it goes over how to upload a program to the remote. There are some key steps that need to be followed exactly in order for the remote to be in upload mode.
The timeout error usually indicates the remote is not in upload mode. (Blinking blue led on the right side & BLE module not flashing red)
The other possible error is selecting the computers internal Bluetooth port and not the /dev/cu..SLAB_USBtoUART
Please let me know if you have any other questions.
@akihiro Hi Akihiro, sorry about the slower response! We have a few people out of the office this week. Let me have Sheila prep a return label for you. That sounds like it was a defective set, so we'll just replace that for you.
@Guled30 I sent you a link to the website where you can install the USB driver for your operating system 🙂 When you download the files, extract them and run the driver disk. Inside there is a separate folder for the "Legacy" version. For your machine, you will most likely need to run this version, sometimes twice. This will allow your code to upload to CoDrone. Let me know if you have any more questions.0_1566324632880_Screen Shot 2019-08-20 at 11.08.30 AM.png
@brennsteph You can build any track you would like and use basic driving commands found here to navigate! To learn how to use IR sensors and camera to make decisions while driving, you can follow our tutorials on Workbench. If you don't want to make your own field, you can purchase one here from us. If you are still having doubts or technical issues, use this link to set up a time and I would happy to speak with you. I hope this helps!
Glad the unhook/rehook option helped you.
there isn't a way in the codrone library to test different arm motors. without seeing the arms, it is hard to determine if there is a contact issue, wiring, or ESC
ya, the landing is a tad tough sometimes. I'll do some runs of dropping the throttle in stages then land and see how that goes. though I've seen when flying and using throttling, the min distance is roughly 20cm (200mm) and the CoDrone likes that gap. forcing it lower will be interesting to see (I've tested going higher because the landscape I'm flying over had buildings [HO gauge table top] and the drone's flight goes up and down which alters the straight line path).
calibrate(): I've found this only works the first time called (doesn't takeoff/land like the instruction says though) successive calls to calibrate() (I was gauging power levels @1 sec to get a feel of distance it travels and how straight of a line it goes) and I had a loop set int he program with successive calibrate()s but the first call changed the lights/paused, but each other successive calls did not.
Also, did you try using the "zero-out" blocks I sent in the previous message? Try putting those blocks together, then clicking those as they're linked together a few times so it "zeroes out" the variables.
As I mentioned, updating the firmware to 50.18 will also work, and it's the more permanent solution.
Also, can you confirm that calibration has been working? As in, it takes off, hovers for 5 seconds, and lands?