Installing autotest on windows

Current version of Django supported by autotest: 1. If you plan on testing your own autotest branch, make sure to set -t to a. Useful if using a modified. To avoid the basename expression to be evaluated.

These packages must be obtained from python pip:. Turns out the problem "AttributeError: 'module' object has no attribute 'default'". If we needed a third port, we could add it as shown:. Mission Planner can then be used to control the simulated vehicle in exactly the same way as though it were a real vehicle. This is where we can change the mode and set commands. Select Guided in the Mode selection list and then press the Set Mode button. Run the file in the Cygwin Terminal , specifying a home position and vehicle model as shown below:.

Click through the remote host and remote Port prompts as these default to the correct values. The MAVProxy 1. This can be found on the right side of the screen on each Github repository home page but in general the URL is:. The build may fail if the file path to some files is too long. If the build fails, please try cloning ArduPilot into a directory very high in the directory structure i.

If during the build process you get an error of missing packet xyz, re-check that you have installed all Cygwin packages listed above. You can run SITL just as you can with any other build environment. To see the terminal, you should install VcXsrv or another X server application for Windows. You have to run syncdb twice, due to peculiarities of the way syncdb works on Django. In order to fix this, you can run the following commands to allow execution of the cgi scripts on your server.

Note: If you are having weird problems with installing autotest, you might want to turn off SElinux to see if the problem is related to it, and then think of a sensible solution to resolve it.

As root:. You can even close the terminal window with screen running, it will keep the babysitter process alive. In order to troubleshoot problems, you can pick up the log file that autotest-scheduler-watcher prints and follow it with tail. This way you might know what happened with a particular scheduler instance.

Clients are managed in the tab hosts of the web frontend.