[erlang-questions] Crazyflie and Erlang: Anyone already playing with this? (Triggered by "Erlang for youngsters")

[Tony Rogvall]

On 17 jun 2014, at 21:35, Boris Mühmer <boris.muehmer@REDACTED> wrote:

> Well, the Crazyflie is like an Andruino on "wings"... I didn't want to run Erlang on top of it. Instead I want to interface the Crazyradio: model the controllable parts of the Crazyflie as "processes", interact with them, which in turn communicate using the Crazyradio to control the Crazyflie.
> 
A client would probably be easy enough to hack.

> Somewhere on the Bitcraze web-site was a hint to put a Raspberry Pi on top of the Crazyflie. Maybe run Erlang on the Rasperry Pi to autonomously control the Crazyflie. On the other hand, this may be too big for an Raspberry Pi... or it may be too slow.
> 
Sound like a cool enough idea. If the copter can carry the Raspberry Pi and an extra battery. Why not.
(A bit strange but fun ... :-)

> I couldn't find much information about the AR.Drone. I even think, that somewhere in the SDK was a passage, that developers aren't allowed to fiddle with the internals/firmware; that was something quite surprising, with what can be seen in the "Drone In-flight Firmware Upgrade" video.
> 
Oops, but it is my property and I want to destroy. We we asked for permission but never got a reply.
If it gets "big", I guess they will probably ask me to remove it. And yes, I did do some (easy) reverse engineering to
figure out where the gpio/uart/i2c was located etc. But they are using linux so they must supply any software 
modification they do...

/Tony

> 
> Regards,
> Boris
> 
> 
> 
> 
> 2014-06-17 21:10 GMT+02:00 Tony Rogvall <tony@REDACTED>:
> Sadly enough the Cazyflie only has 20Kb RAM and 128Kb flash.
> This is, sadly enough, too small for Erlang.
> 
> You could probably implement the client, I did both the client for the regular firmware
> (and a plenty of porting and hacking for the onboard Erlang  controller firmware for the AR.Drone.)
> And that was a plenty of fun as well.
> 
> /Tony
> 
> On 17 jun 2014, at 20:12, Boris Mühmer <boris.muehmer@REDACTED> wrote:
> 
>> My interest in quadcopters started with the following videos (in chronological order I watched them):
>> 1) Raffaello D'Andrea: The astounding athletic power of quadcopters:
>>    https://www.youtube.com/watch?v=w2itwFJCgFQ
>> 2) Drone In-flight Firmware Upgrade:
>>    https://www.youtube.com/watch?v=96UzSHyp0F8
>> 3) Crazyflie Nano Quadcopter pre-release video:
>>    https://www.youtube.com/watch?v=3WBUVYZkODI
>> 
>> After watching 1) and my first searches for quadcopters resulted in quite some interesting models, but somehow there were too "professional", especially when looking at the price tag.
>> 
>> The Parrot AR.Drone 2 (I believe it was used in video 2) isn't that cheap, but it suited the price I had in mind much better (and Erlang was used to interface it, if I didn't get that part wrong), but still I thought it was too large for playing around in a small room and the system was too "closed".
>> 
>> Then I found the Crazyflie project (http://www.bitcraze.se/). Here is a list of things I liked about it:
>>  - it is very small (perfect for indoor tests)
>>  - it is cheap
>>  - it is an open platform
>>  - the range for the radio is up to 80 meters (looks like I need to get a larger flat)
>> 
>> So my questions boils down to this: Is there anyone (beside the feuerlab guys) already fiddling around with Erlang and the Crazyflie (or other quadcopters)?
>> 
>> 
>> Regards
>> Boris
>> 
>> PS: Also have a look at this video "Crazyflie Nano Quadcopter - Assembly video"
>>     http://www.youtube.com/watch?v=kS3qR1IjeGE
>> PPS: Reading the "Handbook of Neuroevolution Through Erlang" (http://www.springer.com/computer/swe/book/978-1-4614-4462-6) gave me even more crazy ideas.
>> 
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
> 
> "Installing applications can lead to corruption over time. Applications gradually write over each other's libraries, partial upgrades occur, user and system errors happen, and minute changes may be unnoticeable and difficult to fix"
> 
> 
> 
> 

"Installing applications can lead to corruption over time. Applications gradually write over each other's libraries, partial upgrades occur, user and system errors happen, and minute changes may be unnoticeable and difficult to fix"



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140617/e7edad28/attachment.htm>