DOC: Getting Started - content and structural issues about dronekit-python HOT 5 CLOSED

One thing not clear in current docs is that you can develop your companion computer APP on the PC/SITL. The APP is "the same" - the only reason you run it on a companion computer is if you need significant computation, low latency from code running to commands reaching the autopilot, and/or "always available even if link to ground station breaks" connectivity.

from dronekit-python.

The commands you are expected to enter look like this:

STABILIZE>param load ../Tools/autotest/copter_params.parm

But the "STABILIZE>" is not displayed in MAVLINK in my vagrant/SITL setup. Instead you get a stream of information from the autopilot. If however you copy in "param load ../Tools/autotest/copter_params.parm" to the prompt then hit enter, the STABILIZE> prompt is briefly displayed as the information is processed.

So shouldn't the "STABILIZE>" bit be removed from the instructions or is this in a "standard setup", and I'm just missing it because I'm on Windows talking to sitl on linux?

from dronekit-python.

There is some inconsistency on whether components are installed as root ( sudo app-get install) or not

• Linux dependency and mavpoxy do use the sudo
• dronekit does not.

I got an error installing dronekit without sudo on my vagrant box, so arguably it should be sudo. However if you're on Windows or Mac you won't use sudo. Thoughts?

from dronekit-python.

Ramon expects to have a SITL vagrant image that can vastly simplify this process by Friday. At that point will revisit the instructions.

from dronekit-python.

Closing this - superseded by #76 76

from dronekit-python.