Does not find mavproxy.py


#1

Hi,
I just started the course and have followed the installation process in the video. When I try to run

sim_vehicle.py --map --console

I get this message

SIM_VEHICLE: Start
SIM_VEHICLE: Killing tasks
SIM_VEHICLE: Starting up at SITL location
SIM_VEHICLE: WAF build
SIM_VEHICLE: Configure waf
SIM_VEHICLE: “/home/droneprograming/courseRoot/apm/ardupilot/modules/waf/waf-light” “configure” “–board” “sitl”
Setting top to : /home/droneprograming/courseRoot/apm/ardupilot
Setting out to : /home/droneprograming/courseRoot/apm/ardupilot/build
Autoconfiguration : enabled
Setting board to : sitl
Using toolchain : native
Checking for ‘g++’ (C++ compiler) : /usr/bin/g++
Checking for ‘gcc’ (C compiler) : /usr/bin/gcc
Checking for c flags ‘-MMD’ : yes
Checking for cxx flags ‘-MMD’ : yes
Checking for need to link with librt : not necessary
Checking for feenableexcept : yes
Checking for HAVE_CMATH_ISFINITE : yes
Checking for HAVE_CMATH_ISINF : yes
Checking for HAVE_CMATH_ISNAN : yes
Checking for NEED_CMATH_ISFINITE_STD_NAMESPACE : yes
Checking for NEED_CMATH_ISINF_STD_NAMESPACE : yes
Checking for NEED_CMATH_ISNAN_STD_NAMESPACE : yes
Checking for header endian.h : yes
Checking for header byteswap.h : yes
Checking for HAVE_MEMRCHR : yes
Checking for program ‘python’ : /usr/bin/python
Checking for python version >= 2.7.0 : 2.7.17
Checking for program ‘python’ : /usr/bin/python
Checking for python version >= 2.7.0 : 2.7.17
Source is git repository : yes
Update submodules : yes
Checking for program ‘git’ : /usr/bin/git
Checking for program ‘size’ : /usr/bin/size
Benchmarks : disabled
Unit tests : enabled
Scripting : enabled
Scripting runtime checks : enabled
Checking for program ‘rsync’ : /usr/bin/rsync
‘configure’ finished successfully (1.220s)
SIM_VEHICLE: Building
SIM_VEHICLE: “/home/droneprograming/courseRoot/apm/ardupilot/modules/waf/waf-light” “build” “–target” “bin/arducopter”
Waf: Entering directory /home/droneprograming/courseRoot/apm/ardupilot/build/sitl' Embedding file sandbox.lua:libraries/AP_Scripting/scripts/sandbox.lua Waf: Leaving directory/home/droneprograming/courseRoot/apm/ardupilot/build/sitl’

BUILD SUMMARY
Build directory: /home/droneprograming/courseRoot/apm/ardupilot/build/sitl
Target Text Data BSS Total

bin/arducopter 2435910 100272 72904 2609086

Build commands will be stored in build/sitl/compile_commands.json
‘build’ finished successfully (1.229s)
SIM_VEHICLE: Using defaults from (/home/droneprograming/courseRoot/apm/ardupilot/Tools/autotest/default_params/copter.parm)
SIM_VEHICLE: Run ArduCopter
SIM_VEHICLE: “/home/droneprograming/courseRoot/apm/ardupilot/Tools/autotest/run_in_terminal_window.sh” “ArduCopter” “/home/droneprograming/courseRoot/apm/ardupilot/build/sitl/bin/arducopter” “-S” “-I0” “–model” “+” “–speedup” “1” “–defaults” “/home/droneprograming/courseRoot/apm/ardupilot/Tools/autotest/default_params/copter.parm”
SIM_VEHICLE: Run MavProxy
SIM_VEHICLE: “mavproxy.py” “–master” “tcp:127.0.0.1:5760” “–sitl” “127.0.0.1:5501” “–out” “127.0.0.1:14550” “–out” “127.0.0.1:14551” “–map” “–console”
RiTW: Starting ArduCopter : /home/droneprograming/courseRoot/apm/ardupilot/build/sitl/bin/arducopter -S -I0 --model + --speedup 1 --defaults /home/droneprograming/courseRoot/apm/ardupilot/Tools/autotest/default_params/copter.parm
[Run MavProxy] An exception has occurred with command: ‘mavproxy.py --master tcp:127.0.0.1:5760 --sitl 127.0.0.1:5501 --out 127.0.0.1:14550 --out 127.0.0.1:14551 --map --console’
[Errno 2] No such file or directory
SIM_VEHICLE: Killing tasks

Option “-e” is deprecated and might be removed in a later version of gnome-terminal.

Use “-- ” to terminate the options and put the command line to execute after it.

It looks like it dosen’t find the mavproxy.py
I can confirm that the file exist.
Any suggestions on how to fix this?


Ubuntu 18.04.6 (course build); "Launch QGC with DK script part3" mode GUIDED loop hanging (launchSitl basic_template.py)
#2

A reboot seemed to fix it…

However, the link will not come up.


#3

Apparently there is a bug in ardupilot 4.0.3 in regards to stack overflow ftp.
Used 4.0.6 instead, and it worked fine.


#4

Glad you got that figured out, @haugerik !

Good to know in case others stumble across this problem.


closed #5