search

fselius / qtcopter

2 stars 0 forks source link

References for other projects #52

Open serbuh opened 9 years ago

serbuh commented 9 years ago

I am strongly convinced that we should look more on other projects like in order to learn from other's experience. I think that this is the best approach with our system which is highly sensitive for crashes. So while I'm procrastinating at the exams period - I'll post here some ideas, links and etc.

Here there is a reference for a Red Balloon Finder Project. python code that runs on the odroid Slightly modified Copter-3.2 code Video example

You are welcomed to comment and to discuss about their approach. I think that at the end we will be forced (by ourselves) to make small changes in the firmware too:)

fselius commented 9 years ago

I'm ambivalent about this approach. I don't like it that the API has to run through mavproxy, I prefer the ROS approach - every node runs on a different process, instead of a single python script that does everything. You could expose the API to external processes using TCP/pipes/etc(Similarly to mavros) but you'd still be running that API inside mavproxy. On the other hand, it looks like ROS adds noticeable latencies which are likely to cause problems when guiding the drone.

I'm going to try that API on the micro-drone if time allows it and compare it to mavros.

fselius commented 9 years ago

Another interesting option is using cleanflight, it's a basic flight controller with a cool feature - it supports Oneshot for ESCs. ESCs with oneshot can actively slow down the propellers, unlike regular ESCs that rely on the air resistance to passively slow down the propellers. This could mean better accuracy over drone movement.