Major problem when installing "SITL" on Windows

hfai2016 · January 23, 2016, 8:18pm

I got the following Error:
Could anyone help please?

[code]HFAI@PC ~/ardupilot/ArduCopter
$ git clone git://github.com/diydrones/ardupilot.git
Cloning into ‘ardupilot’…
remote: Counting objects: 144648, done.
remote: Compressing objects: 100% (59/59), done.
remote: Total 144648 (delta 29), reused 0 (delta 0), pack-reused 144589
Receiving objects: 100% (144648/144648), 74.98 MiB | 99.00 KiB/s, done.
Resolving deltas: 100% (103620/103620), done.
Checking connectivity… done.
Checking out files: 100% (2253/2253), done.

HFAI@PC ~/ardupilot/ArduCopter
$ make sitl -j4
echo "Generating MAVLink headers…"
Checking modules
Generating MAVLink headers…
#goto mavlink module directory and run the most recent generator script
echo “Generating C code using mavgen.py located at” /home/HFAI/ardupilot/modules/mavlink/
Generating C code using mavgen.py located at /home/HFAI/ardupilot/modules/mavlink/
PYTHONPATH=/home/HFAI/ardupilot/modules/mavlink/ python /home/HFAI/ardupilot/modules/mavlink//pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 - -output=/tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0 /home/HFAI/ardupilot/modules/mavlink//message_definitions/v1.0/ardupilotmega. xml
// BUILDROOT=/tmp/ArduCopter.build HAL_BOARD=HAL_BOARD_SITL HAL_BOARD_SUBTYPE=HAL_BOARD_SUBTYPE_NONE TOOLCHAIN=NATIVE EXTRAFLAGS=-DGIT_VERSION="e78595 bf"
Validating /home/HFAI/ardupilot/modules/mavlink//message_definitions/v1.0/ardupilotmega.xml
Parsing /home/HFAI/ardupilot/modules/mavlink//message_definitions/v1.0/ardupilotmega.xml
Note: message DATA64 is longer than 64 bytes long (74 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transf er unit.
Note: message DATA96 is longer than 64 bytes long (106 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air trans fer unit.
Note: message REMOTE_LOG_DATA_BLOCK is longer than 64 bytes long (214 bytes), which can cause fragmentation since many radio modems use 64 bytes as ma ximum air transfer unit.
Validating /home/HFAI/ardupilot/modules/mavlink//message_definitions/v1.0/common.xml
Parsing /home/HFAI/ardupilot/modules/mavlink//message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air t ransfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (76 bytes), which can cause fragmentation since many radio modems use 64 bytes as m aximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (193 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (237 bytes), which can cause fragmentation since many radio modems use 64 bytes as m aximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air t ransfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air tr ansfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air tra nsfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as m aximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maxi mum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air tra nsfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum ai r transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximu m air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as max imum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 176 MAVLink message types in 2 XML files
Generating C implementation in directory /tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega
Generating C implementation in directory /tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/common
Copying fixed headers
D:/SOS/ArduPilot/Cygwin/home/HFAI/ardupilot/mk/mavgen.mk:9: recipe for target ‘/tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupi lotmega/mavlink.h’ failed
make: *** [/tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h] Aborted (core dumped)
make: *** Deleting file ‘/tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h’
[/code]

hfai2016 · January 24, 2016, 12:11pm

Any help pls ?

craigo · January 25, 2016, 10:50pm

I am following the same instructions and getting the same error.

I have previously had SITL working on my Windows 7 computer, usable with the MAVProxy Console, Mission Planner and Tower. Yesterday I fired it up for the first time in a month or two, and it no longer worked. So I updated MAVProxy (v1.4.38, successful), updated cygwin (successful), recreated the local ardupilot git repository (successful) and attempted to rebuild:

user@computer ~/ardupilot/ArduCopter
$ make sitl -j4
make: *** No rule to make target '/home/user/ardupilot/modules/mavlink/message_definitions/v1.0/ardupilotmega.xml', needed by '/tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h'.  Stop.
make: *** Waiting for unfinished jobs....
Checking modules
modules/PX4Firmware/.git missing - need module init
+ git submodule init
// BUILDROOT=/tmp/ArduCopter.build HAL_BOARD=HAL_BOARD_SITL HAL_BOARD_SUBTYPE=HAL_BOARD_SUBTYPE_NONE TOOLCHAIN=NATIVE EXTRAFLAGS=-DGIT_VERSION="68cf1b69"
Submodule 'modules/PX4Firmware' (git://github.com/diydrones/PX4Firmware.git) registered for path 'modules/PX4Firmware'
Submodule 'modules/PX4NuttX' (git://github.com/diydrones/PX4NuttX.git) registered for path 'modules/PX4NuttX'
Submodule 'modules/gbenchmark' (git://github.com/google/benchmark.git) registered for path 'modules/gbenchmark'
Submodule 'gtest' (git://github.com/diydrones/googletest) registered for path 'modules/gtest'
Submodule 'modules/mavlink' (git://github.com/diydrones/mavlink) registered for path 'modules/mavlink'
Submodule 'modules/uavcan' (git://github.com/diydrones/uavcan.git) registered for path 'modules/uavcan'
Submodule 'modules/waf' (git://github.com/diydrones/waf.git) registered for path 'modules/waf'
+ git submodule update
Cloning into 'modules/PX4Firmware'...
remote: Counting objects: 140251, done.
remote: Compressing objects: 100% (14/14), done.
remote: Total 140251 (delta 29), reused 28 (delta 28), pack-reused 140209
Receiving objects: 100% (140251/140251), 69.94 MiB | 224.00 KiB/s, done.
Resolving deltas: 100% (103599/103599), done.
Checking connectivity... done.
Submodule path 'modules/PX4Firmware': checked out 'c1323c55fa8e2657144a1f2202d7c0492b8acde3'
Cloning into 'modules/PX4NuttX'...
remote: Counting objects: 125508, done.
remote: Total 125508 (delta 0), reused 0 (delta 0), pack-reused 125508
Receiving objects: 100% (125508/125508), 31.15 MiB | 224.00 KiB/s, done.
Resolving deltas: 100% (101978/101978), done.
Checking connectivity... done.
Submodule path 'modules/PX4NuttX': checked out 'd48fa3072b2396c489966c4ab10183ac7cf3dea9'
Cloning into 'modules/gbenchmark'...
remote: Counting objects: 1788, done.
remote: Total 1788 (delta 0), reused 0 (delta 0), pack-reused 1788
Receiving objects: 100% (1788/1788), 451.10 KiB | 226.00 KiB/s, done.
Resolving deltas: 100% (1078/1078), done.
Checking connectivity... done.
Submodule path 'modules/gbenchmark': checked out '006d23ccca1375a973b7fae0cc351cedb41b812a'
Cloning into 'modules/gtest'...
remote: Counting objects: 7141, done.
remote: Total 7141 (delta 0), reused 0 (delta 0), pack-reused 7141
Receiving objects: 100% (7141/7141), 2.61 MiB | 223.00 KiB/s, done.
Resolving deltas: 100% (5306/5306), done.
Checking connectivity... done.
Submodule path 'modules/gtest': checked out 'c99458533a9b4c743ed51537e25989ea55944908'
Cloning into 'modules/mavlink'...
remote: Counting objects: 12783, done.
remote: Total 12783 (delta 0), reused 0 (delta 0), pack-reused 12783
Receiving objects: 100% (12783/12783), 6.07 MiB | 271.00 KiB/s, done.
Resolving deltas: 100% (8087/8087), done.
Checking connectivity... done.
Submodule path 'modules/mavlink': checked out 'c47a4e6e1d008baa7af20818906b8275df49694d'
Cloning into 'modules/uavcan'...
remote: Counting objects: 9510, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 9510 (delta 0), reused 0 (delta 0), pack-reused 9508
Receiving objects: 100% (9510/9510), 1.41 MiB | 268.00 KiB/s, done.
Resolving deltas: 100% (6253/6253), done.
Checking connectivity... done.
Submodule path 'modules/uavcan': checked out '6dd432c9742c22e1dd1638c7f91cf937e4bdb2f1'
Cloning into 'modules/waf'...
remote: Counting objects: 9959, done.
remote: Total 9959 (delta 0), reused 0 (delta 0), pack-reused 9959
Receiving objects: 100% (9959/9959), 2.84 MiB | 269.00 KiB/s, done.
Resolving deltas: 100% (6739/6739), done.
Checking connectivity... done.
Submodule path 'modules/waf': checked out '878ab1e29494e28236a260212a5021b1de35d9a3'
+ cat
==============================
git submodules are initialised

Please see http://dev.ardupilot.com/wiki/git-submodules/

Please restart the build
==============================
+ exit 1
C:/cygwin/home/user/ardupilot/mk/modules.mk:8: recipe for target 'CHECK_MODULES' failed
make: *** [CHECK_MODULES] Error 1

To my untrained eye this looks like the make command tries to make modules that initially aren’t present, so it calls git to download them, tells the user to restart the build, and produces the “CHECK_MODULES” error.

When I retry the build, I get the following, along the same lines as hfai2016:

user@computer ~/ardupilot/ArduCopter
$ make sitl -j4
echo "Generating MAVLink headers..."
Checking modules
Generating MAVLink headers...
#goto mavlink module directory and run the most recent generator script
echo "Generating C code using mavgen.py located at" /home/user/ardupilot/modules/mavlink/
Generating C code using mavgen.py located at /home/user/ardupilot/modules/mavlink/
PYTHONPATH=/home/user/ardupilot/modules/mavlink/ python /home/user/ardupilot/modules/mavlink//pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=/tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0 /home/user/ardupilot/modules/mavlink//message_definitions/v1.0/ardupilotmega.xml
// BUILDROOT=/tmp/ArduCopter.build HAL_BOARD=HAL_BOARD_SITL HAL_BOARD_SUBTYPE=HAL_BOARD_SUBTYPE_NONE TOOLCHAIN=NATIVE EXTRAFLAGS=-DGIT_VERSION="68cf1b69"
Validating /home/user/ardupilot/modules/mavlink//message_definitions/v1.0/ardupilotmega.xml
Parsing /home/user/ardupilot/modules/mavlink//message_definitions/v1.0/ardupilotmega.xml
Note: message DATA64 is longer than 64 bytes long (74 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DATA96 is longer than 64 bytes long (106 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message REMOTE_LOG_DATA_BLOCK is longer than 64 bytes long (214 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validating /home/user/ardupilot/modules/mavlink//message_definitions/v1.0/common.xml
Parsing /home/user/ardupilot/modules/mavlink//message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (76 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (193 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (237 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 176 MAVLink message types in 2 XML files
Generating C implementation in directory /tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega
Generating C implementation in directory /tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/common
Copying fixed headers
C:/cygwin/home/user/ardupilot/mk/mavgen.mk:9: recipe for target '/tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h' failed
make: *** [/tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h] Aborted (core dumped)
make: *** Deleting file '/tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h'

Besides the many warnings about various messages being longer than 64 bytes (is this a problem?), the main errors appear to be the third-to-last and second-to-last lines of the make command output.

My PATH variable is correct; it includes the /ardupilot/Tools/autotest directory.

Am also unsure how to proceed.

jose_luis · January 26, 2016, 6:12pm

I think I’m having the same problem when using sim_vehicle.sh in Windows. These are the steps I followed:

$ sim_vehicle.sh -j4 --map
~/ardupilot/arducopter ~/ardupilot/arducopter
Building sitl
Checking modules
echo "Generating MAVLink headers…"
Generating MAVLink headers…
#goto mavlink module directory and run the most recent generator script
echo “Generating C code using mavgen.py located at” /home/casa/ardupilot/modules/mavlink/
Generating C code using mavgen.py located at /home/casa/ardupilot/modules/mavlink/
PYTHONPATH=/home/casa/ardupilot/modules/mavlink/ python /home/casa/ardupilot/modules/mavlink//pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=/tmp/arducopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0 /home/casa/ardupilot/modules/mavlink//message_definitions/v1.0/ardupilotmega.xml
// BUILDROOT=/tmp/arducopter.build HAL_BOARD=HAL_BOARD_SITL HAL_BOARD_SUBTYPE=HAL_BOARD_SUBTYPE_NONE TOOLCHAIN=NATIVE EXTRAFLAGS=-DGIT_VERSION="417176c0"
Validating /home/casa/ardupilot/modules/mavlink//message_definitions/v1.0/ardupilotmega.xml
Parsing /home/casa/ardupilot/modules/mavlink//message_definitions/v1.0/ardupilotmega.xml
Note: message DATA64 is longer than 64 bytes long (74 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DATA96 is longer than 64 bytes long (106 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message REMOTE_LOG_DATA_BLOCK is longer than 64 bytes long (214 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validating /home/casa/ardupilot/modules/mavlink//message_definitions/v1.0/common.xml
Parsing /home/casa/ardupilot/modules/mavlink//message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (76 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (193 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (237 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 176 MAVLink message types in 2 XML files
Generating C implementation in directory /tmp/arducopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega
Generating C implementation in directory /tmp/arducopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/common
Copying fixed headers
C:/cygwin/home/casa/ardupilot/mk/mavgen.mk:9: fallo en las instrucciones para el objetivo '/tmp/arducopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h’
make: *** [/tmp/arducopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h] Aborted (core dumped) [Núcleo vaciado a un archivo]
make: *** Se borra el archivo '/tmp/arducopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h’
make: *** Se espera a que terminen otras tareas…
echo "Generating MAVLink headers…"
Checking modules
Generating MAVLink headers…
#goto mavlink module directory and run the most recent generator script
echo “Generating C code using mavgen.py located at” /home/casa/ardupilot/modules/mavlink/
Generating C code using mavgen.py located at /home/casa/ardupilot/modules/mavlink/
PYTHONPATH=/home/casa/ardupilot/modules/mavlink/ python /home/casa/ardupilot/modules/mavlink//pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=/tmp/arducopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0 /home/casa/ardupilot/modules/mavlink//message_definitions/v1.0/ardupilotmega.xml
Validating /home/casa/ardupilot/modules/mavlink//message_definitions/v1.0/ardupilotmega.xml
// BUILDROOT=/tmp/arducopter.build HAL_BOARD=HAL_BOARD_SITL HAL_BOARD_SUBTYPE=HAL_BOARD_SUBTYPE_NONE TOOLCHAIN=NATIVE EXTRAFLAGS=-DGIT_VERSION="417176c0"
Parsing /home/casa/ardupilot/modules/mavlink//message_definitions/v1.0/ardupilotmega.xml
Note: message DATA64 is longer than 64 bytes long (74 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DATA96 is longer than 64 bytes long (106 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message REMOTE_LOG_DATA_BLOCK is longer than 64 bytes long (214 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validating /home/casa/ardupilot/modules/mavlink//message_definitions/v1.0/common.xml
Parsing /home/casa/ardupilot/modules/mavlink//message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (76 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (193 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (237 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 176 MAVLink message types in 2 XML files
Generating C implementation in directory /tmp/arducopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega
Generating C implementation in directory /tmp/arducopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/common
Copying fixed headers
C:/cygwin/home/casa/ardupilot/mk/mavgen.mk:9: fallo en las instrucciones para el objetivo '/tmp/arducopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h’
make: *** [/tmp/arducopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h] Aborted (core dumped) [Núcleo vaciado a un archivo]
make: *** Se borra el archivo '/tmp/arducopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h’
make: *** Se espera a que terminen otras tareas…
/home/casa/ardupilot/Tools/autotest/sim_vehicle.sh: Build failed

rmackay9 · January 27, 2016, 6:09am

I think removing the “-j4” would be a good thing to try. I always run SITL on an Ubuntu virtual machine on my Windows box. There are instructions on how to do that on the developer wiki. SITL is suppose to work on Windows but I haven’t personally tried it.

jose_luis · January 27, 2016, 6:26am

I’ve tried removing -j4 but the result is still the same

craigo · January 27, 2016, 8:26am

Thanks rmackay9. I tried rebuilding from scratch and omitting the “-j4” switch, with the exact same results.

SITL did work on Windows previously… I don’t know why it isn’t working now. It’s such a useful tool and I want it back!

I’ll consider using a Linux VM as a last resort, but would prefer the native Windows stuff to work.

craigo · February 2, 2016, 10:22am

I retried again this evening, completely reinstalling cygwin and MAVProxy, which had updated to 1.4.40. I had the same errors.

Has the code been refactored into modules recently? If so, my suspicion is that this is where the problem lies - at least on Windows. In the past, I don’t recall there being any mention of modules when building, and certainly no errors - module-related or otherwise.

Do these errors point to the cause(s) of the problem?

[ul]
[li]C:/cygwin/home/user/ardupilot/mk/modules.mk:8: recipe for target ‘CHECK_MODULES’ failed[/li]
[li]make: *** [CHECK_MODULES] Error 1[/li]
[li]C:/cygwin/home/user/ardupilot/mk/mavgen.mk:9: recipe for target ‘/tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h’ failed[/li]
[li]make: *** [/tmp/ArduCopter.build/libraries/GCS_MAVLink/include/mavlink/v1.0/ardupilotmega/mavlink.h] Aborted (core dumped)[/li][/ul]

ddomit · February 7, 2016, 3:19pm

I have the same problem!

Has anyone found a solution?

Thanks

craigo · February 7, 2016, 8:42pm

This was raised as issue 3586 on the project’s github page. There is a workaround posted there that you can use to get SITL working again.