@vette99 You're right! We have a few edits we need to make to the docs. We'll make sure to update that. @robolink_whoseop can you make sure to fix the docs, and the library so they all use "takeoff()" instead of "takeOff()"?
Good catch, @vette99!
We've disabled the Chrome app's firmware update feature on the latest version (1.1.6 as of this post), since the bug seems to be a bit more persnickety than we anticipated. In the meantime, the most reliable way to update the CoDrone firmware would be to use our partner's "Petrone" app, which is available on Android and iOS.
The latest CoDrone firmware version is 50.18, and it has an important zero-out feature that prevents variables from a previous flight sequence from carrying over to the next flight sequence after you've hit a killswitch. Namely, if you ran a pitch = 70, then hit a killswitch, the old version might have pitch = 70 again when you run the sequence again.
You can see the tutorial for how to do that in 1H: Updating CoDrone at step #3.
@Kirthi That's amazing to hear. I just saw the thread that you had with @robolink_hansol and @robolink_grace, and I'm glad we were able to help out.
Please let us know how else we can support for the upcoming workshop
Also, I just read that you're a junior in high school. It's an inspiration to see you flexing your entrepreneurial muscle at such a young age already!