@Coolaswa wrote:

Hello,

I tried to compile arducopter and I got an error related to uavcan apparently.

[14/15] CMake Build px4 msg_gen
No such file or directory
CMake Error: Generator: execution of make failed. Make command was: “” “msg_gen”

Compiler failure
Traceback (most recent call last):
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/init.py”, line 300, in enum_last_value
last = next(it)
StopIteration

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/init.py”, line 107, in run_generator
text = generate_one_type(template_expander, t)
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/init.py”, line 239, in generate_one_type
text = template_expander(t=t) # t for Type
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/init.py”, line 307, in expand
return template(**args)
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/pyratemp.py”, line 1030, in call
u = “”.join(self._render(self.parsetree, self.current_data))
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/pyratemp.py”, line 1130, in render
output.extend(self.render(elem[2], data))
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/pyratemp.py”, line 1104, in render
output.append(unicode(_eval(elem[1], data)))
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/pyratemp.py”, line 1079, in _eval
return self.evalfunc(expr, data)
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/pyratemp.py”, line 884, in eval
x = eval(self.compile(expr), {“builtins”:self.eval_allowed_globals}, locals)
File “”, line 1, in
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/pyratemp.py”, line 1030, in call
u = “”.join(self._render(self.parsetree, self.current_data))
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/pyratemp.py”, line 1104, in render
output.append(unicode(_eval(elem[1], data)))
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/pyratemp.py”, line 1079, in _eval
return self.evalfunc(expr, data)
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/pyratemp.py”, line 884, in eval
x = eval(self.compile(expr), {“builtins”:self.eval_allowed_globals}, locals)
File “”, line 1, in
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/pyratemp.py”, line 1030, in call
u = “”.join(self._render(self.parsetree, self.current_data))
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/pyratemp.py”, line 1138, in render
output.extend(self.render(elem[1], data))
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/pyratemp.py”, line 1119, in render
for i in loop_iter:
RuntimeError: generator raised StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdlc”, line 61, in
dsdlc_run(args.source_dir, args.incdir, args.outdir)
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/init.py”, line 62, in run
run_generator(types, output_dir)
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/init.py”, line 111, in run_generator
die(ex)
File “/home/michiel/ardupilot/modules/uavcan/libuavcan/dsdl_compiler/libuavcan_dsdl_compiler/init.py”, line 89, in die
raise DsdlCompilerException(str(text))
libuavcan_dsdl_compiler.DsdlCompilerException: generator raised StopIteration
generator raised StopIteration

uavcangen returned 1 error code

I am running arch linux, uavcan is installed in both pip2 and pip3. (The error occured before I installed those as well).

Anyone got any tips for me?

Thanks in advance,
Michiel

Posts: 3

Participants: 2

Read full topic

@nhardy wrote:

Hi All,

I was wondering if someone would be able to shed some light on this issue.

We have an X8 copter and are trying to fly very accurate (RTK GPS) low altitude (~5m) small scale missions planned using Auto WP > Survey (Grid) with very high side and forward overlap. The side overlap is no problem, but we’re unable to achieve sufficient forward overlap (80%) using DO_DIGICAM_CONTROL, as Mission Planner seems to limit triggers to a separation of no less than 4m (when travelling along each flight line). At this altitude, we require triggers to be under 1m apart.

When increasing the forward overlap %, the “dist between images” value decreases as expected to less than 4m, but the trigger points on the map are never closer than 4m, and as a result we don’t get enough forward overlap.

I found this post Photo numbers in survey grid but not sure if it’s still relevant as we can get spacing less than 10m, just not 4m?

Ideally we’d like to be able to capture an image every ~25cm along a flight line. We’ve tried CAM_TRIGG_DIST as well, but it appears to be limited to a minimum distance of 1m. If anyone could shed some light on how to overcome this it would be much appreciated.

Using Mission Planner 1.3.59 and 3.5.7 X8 octocopter, and a very low res camera hence the need for low altitude.

Many thanks in advance.

Posts: 1

Participants: 1

Read full topic

@xingxing wrote:

Please look at my log as attached …
After set up for the auto take off ,the plane take off with 15 degree pitch up ,but it did not transfer to auto mode after reach the final height of take off .and It seems out of my control for a while and I can see the telemetry signal disconnect for a several second ,it’s really hard to flight back finally .
I find the pitot tube of airspeed sensor have some problem ,after flight ,witch lead to the monitor airspeed less than real airspeed .

and there is another problem even with airspeed sensor is normal ,that is the plane can’t roll to 60 degree even if I set the roll limited to 60 degree ,it just turn about 40 degree if I push the stick to the end of left

hope someone analysis my log to find out the problem
thaks .https://drive.google.com/file/d/1beoJTTD3G9JEaZ6EchX-YmR5mEFHm7Hm/view?usp=sharing https://drive.google.com/file/d/1s6N0NEKpwYjDOqgxayDTlvUAuXYDs0xP/view?usp=sharing https://drive.google.com/file/d/13fzPoVHd-2AKv5HCiKu5HVtge1VDMXCR/view?usp=sharing https://drive.google.com/file/d/1izjgwEEbF8oEjmBWz3hRg-B6MXAdCE0U/view?usp=sharing

Posts: 2

Participants: 2

Read full topic

@jonathan84clark wrote:

If I turn on reverse thrust (set THR_MIN to -100%) the simulated aircraft simply starts armed and taking off. And on landing it’s speed is much higher. Is reverse thrust simulated?

I got a response on a GitHub defect that I incorrectly used to ask this question. It says:
“reverse thrust is simulated. You do need to start the SITL model with
“-revthrurst”, however.”

Unfortunately when I tried this the simulator complained that option -r is not supported.

Thanks,

Jonathan L Clark

Posts: 1

Participants: 1

Read full topic

@Kashish_Goyal wrote:

Hi,

Bebop2 fails to boot up with the following message (displayed through UART connection):

Booting in mode NAND
jumping to 0x00100000 len 46000
�nand_flash: Toshiba 2048 bytes per page, 1 Gbits (x8), 1.8V, timing ONFI 4
Parrotboot for target MILOS, git version ecos-bootloader-p7-start-343-gb32f66c, built on Dec 14 2015

P7R4
P7MU Revision 2
Crystal Frequency: 26000000 Hz
RAM config name: Milos - Dual NT5CC128M16CP-DI - CL11, CWL8 @750MHz 750 Mhz
Milos rev: 3

but 0
Scaning start 8M (size 16M), page shift 11 eb size 131072
vid_hdr_offset 2048, data_offset 4096 leb_size 126976
image_seq is 64dd480f
new volume 4
new volume 0
new volume 1
parsed 8192 pages
vol0 : main_boot 29/67 ebs
vol1 : alt_boot 36/55 ebs
volume 0 : "main_boot" ok (3682304)
Attempt booting on UBI volume with ID 0...
plf: loading E_TEXT section to addr 0x82000000 size 3661320... done.
plf: loading U_BOOTLOADER section to addr 0x80700000 size 208... done.
Booting Linux...' boxinit.serialno=P742PB2K180000A29220  calib=0x001C0036 mtdparts=nand0:8M(Pbootloader),16M(Pmain_boot),8M(Pfactory),50M(Psystem),46M(Pupdate) console=ttyPA0,115200 loglevel=8 ubi.mtd=Pfactory ubi.mtd=Psystem ubi.mtd=Pupdate root=ubi1:system rootfstype=ubifs quiet androidboot.bootloader=ecos-bootloader-p7-start-343-gb32f66c '
[    1.456621] Kernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[    1.468959] [<c0014530>] (unwind_backtrace+0x0/0xf8) from [<c0496588>] (panic+0x98/0x1e0)
[    1.477090] [<c0496588>] (panic+0x98/0x1e0) from [<c04961a8>] (dump_instr+0x0/0x12c)
[    1.484790] CPU :stop�g
[    1.487475] [<c0014530>] (unwind_backtrace+0x0/0xf8) from [<c0013908>] (handle_IPI+0x2�
[    2.571556] p7-i2cm p7-i2cm.0: i2c fifo mode without irq is not supported
[    2.578474] p7-i2cm p7-i2cm.0: i2c fifo mode without irq is not supported
[    2.585238] p7-i2cm p7-i2cm.0: i2c fifo mode without irq is not supported
[    2.592008] p7-i2cm p7-i2cm.0: i2c fifo mode without irq is not supported

Can you please help me with a way to reflash the Bebop?

Also, is it possible to load a different OS such as Raspbian given that Ardupilot flight stack is standalone binary and should work irrespective of the OS loaded.

@julienberaud

Posts: 1

Participants: 1

Read full topic

@jasonbeach wrote:

I have a couple of Tarot T18’s with pixhawk2’s that have been flying Copter 3.5.2 for a while. I’d like to upgrade to Copter 3.6.0 to fix an altitude drift issue (this PR), however on initially flying it the vehicle seemed less stable than it did on Copter 3.5.2.

Copter 3.5.2 Log
Copter 3.6.0 Log

It wasn’t unstable to the point of crashing or anything, but the gimbal which had been able to stabilize the video when the vehicle had Copter 3.5.2 was not able to do so with Copter 3.6.0. I tried briefly to adjust the gains (decreased roll / pitch rates PI from .2 to .15 and increased the roll / pitch rate D from .01 to .015) but that appeared to make things slightly worse). I was limited on time and wasn’t able to try adjusting the gains in the other direction, but hopefully will this week when I go out and fly. Is there anything between the firmware versions that could cause this?

Thanks

Posts: 1

Participants: 1

Read full topic

@Iron_Donkey wrote:

I’ve got some extra components for sale if anyone is interested, mostly all brand new and unused (free shipping to those in the continental US)

Cube 2.1 mini carrier board - $45 shipped

Cube 2.1 standard sized carrier board - $100 shipped

Pixhawk 3 pro - $215 shipped

I might also have an extra cube lying around but I’ll have to look (brand new) - $145 shipped

3DR Solo upgraded mRo m8n GPS (w/o internal compass) - $35 shipped

and I’ve got around 3 or 4 mRo Pixracer R15 Flight controllers lying around also that I want gone, some of them are used and some are new but I honestly can’t tell which ones are which. $75 shipped each on those.

Shoot me a pm if you’re interested in any of this stuff!

Posts: 1

Participants: 1

Read full topic

@Bart4S wrote:

Hi!

I’m working on creating a plugin, which will
*add seperate tab alongside “Quick”, “Actions”, “Scripts” tabs with payload bay indicators working with Mavlink messages,
*make warning window pop up on certain Mavlink message.

Have uploaded an attachment, hope it’ll clear things up.

mp-markings.jpg1920x1200 466 KB

I’ll be glad if anyone point where, in the MP code, those tabs are implemented, so I can sort out how it’s built.
Of course every tip will be much appretiated!

Thanks in advance.

Posts: 1

Participants: 1

Read full topic

@ben_cd wrote:

Hi,

I am trying to compile ArduSub on Linux Ubuntu 16.04. I have followed all necessary steps from

https://www.ardusub.com/developers/developers.html

This is my output, with cmake related error at the end:

prince@Prince-ThinkPad-W530:~/ardupilot$ ./waf clean
'clean' finished successfully (0.484s)
prince@Prince-ThinkPad-W530:~/ardupilot$ ./waf configure --board px4-v2
Setting top to                           : /home/prince/ardupilot 
Setting out to                           : /home/prince/ardupilot/build 
Autoconfiguration                        : enabled 
Setting board to                         : px4-v2 
Checking for program 'arm-none-eabi-ar'  : /usr/bin/arm-none-eabi-ar 
Using toolchain                          : arm-none-eabi 
Checking for 'g++' (C++ compiler)        : /usr/bin/arm-none-eabi-g++ 
Checking for 'gcc' (C compiler)          : /usr/bin/arm-none-eabi-gcc 
Checking for HAVE_CMATH_ISFINITE         : no 
Checking for HAVE_CMATH_ISINF            : no 
Checking for HAVE_CMATH_ISNAN            : no 
Checking for NEED_CMATH_ISFINITE_STD_NAMESPACE : no 
Checking for NEED_CMATH_ISINF_STD_NAMESPACE    : no 
Checking for NEED_CMATH_ISNAN_STD_NAMESPACE    : no 
Checking for header endian.h                   : not found 
Checking for header byteswap.h                 : not found 
Checking for program 'cmake'                   : /usr/bin/cmake 
Checking cmake version                         : 3.5.1 
Checking for program 'ninja, ninja-build'      : not found 
Checking for program 'make'                    : /usr/bin/make 
Checking for program 'python'                  : /usr/bin/python 
Checking for python version >= 2.7.0           : 2.7.12 
Checking for program 'python'                  : /usr/bin/python 
Checking for python version >= 2.7.0           : 2.7.12 
Source is git repository                       : yes 
Update submodules                              : yes 
Checking for program 'git'                     : /usr/bin/git 
Gtest                                          : PX4 boards currently don't support compiling gtest 
Checking for program 'arm-none-eabi-size'      : /usr/bin/arm-none-eabi-size 
Benchmarks                                     : disabled 
Unit tests                                     : disabled 
'configure' finished successfully (0.653s)
prince@Prince-ThinkPad-W530:~/ardupilot$ ./waf build sub
Waf: Entering directory `/home/prince/ardupilot/build/px4-v2'
[ 5/14] Processing modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
[ 6/14] Processing uavcangen: modules/uavcan/dsdl/uavcan/CoarseOrientation.uavcan modules/uavcan/dsdl/uavcan/Timestamp.uavcan modules/uavcan/dsdl/uavcan/equipment/actuator/1010.ArrayCommand.uavcan modules/uavcan/dsdl/uavcan/equipment/actuator/1011.Status.uavcan modules/uavcan/dsdl/uavcan/equipment/actuator/Command.uavcan modules/uavcan/dsdl/uavcan/equipment/ahrs/1000.Solution.uavcan modules/uavcan/dsdl/uavcan/equipment/ahrs/1001.MagneticFieldStrength.uavcan modules/uavcan/dsdl/uavcan/equipment/air_data/1020.TrueAirspeed.uavcan modules/uavcan/dsdl/uavcan/equipment/air_data/1021.IndicatedAirspeed.uavcan modules/uavcan/dsdl/uavcan/equipment/air_data/1025.AngleOfAttack.uavcan modules/uavcan/dsdl/uavcan/equipment/air_data/1026.Sideslip.uavcan modules/uavcan/dsdl/uavcan/equipment/air_data/1028.StaticPressure.uavcan modules/uavcan/dsdl/uavcan/equipment/air_data/1029.StaticTemperature.uavcan modules/uavcan/dsdl/uavcan/equipment/camera_gimbal/1040.AngularCommand.uavcan modules/uavcan/dsdl/uavcan/equipment/camera_gimbal/1041.GEOPOICommand.uavcan modules/uavcan/dsdl/uavcan/equipment/camera_gimbal/1044.Status.uavcan modules/uavcan/dsdl/uavcan/equipment/camera_gimbal/Mode.uavcan modules/uavcan/dsdl/uavcan/equipment/esc/1030.RawCommand.uavcan modules/uavcan/dsdl/uavcan/equipment/esc/1031.RPMCommand.uavcan modules/uavcan/dsdl/uavcan/equipment/esc/1034.Status.uavcan modules/uavcan/dsdl/uavcan/equipment/gnss/1060.Fix.uavcan modules/uavcan/dsdl/uavcan/equipment/gnss/1061.Auxiliary.uavcan modules/uavcan/dsdl/uavcan/equipment/gnss/1062.RTCMStream.uavcan modules/uavcan/dsdl/uavcan/equipment/hardpoint/1070.Command.uavcan modules/uavcan/dsdl/uavcan/equipment/hardpoint/1071.Status.uavcan modules/uavcan/dsdl/uavcan/equipment/indication/1080.BeepCommand.uavcan modules/uavcan/dsdl/uavcan/equipment/indication/1081.LightsCommand.uavcan modules/uavcan/dsdl/uavcan/equipment/indication/RGB565.uavcan modules/uavcan/dsdl/uavcan/equipment/indication/SingleLightCommand.uavcan modules/uavcan/dsdl/uavcan/equipment/power/1090.PrimaryPowerSupplyStatus.uavcan modules/uavcan/dsdl/uavcan/equipment/power/1091.CircuitStatus.uavcan modules/uavcan/dsdl/uavcan/equipment/power/1092.BatteryInfo.uavcan modules/uavcan/dsdl/uavcan/equipment/range_sensor/1050.Measurement.uavcan modules/uavcan/dsdl/uavcan/equipment/safety/1100.ArmingStatus.uavcan modules/uavcan/dsdl/uavcan/protocol/1.GetNodeInfo.uavcan modules/uavcan/dsdl/uavcan/protocol/2.GetDataTypeInfo.uavcan modules/uavcan/dsdl/uavcan/protocol/341.NodeStatus.uavcan modules/uavcan/dsdl/uavcan/protocol/4.GetTransportStats.uavcan modules/uavcan/dsdl/uavcan/protocol/4.GlobalTimeSync.uavcan modules/uavcan/dsdl/uavcan/protocol/5.Panic.uavcan modules/uavcan/dsdl/uavcan/protocol/5.RestartNode.uavcan modules/uavcan/dsdl/uavcan/protocol/6.AccessCommandShell.uavcan modules/uavcan/dsdl/uavcan/protocol/CANIfaceStats.uavcan modules/uavcan/dsdl/uavcan/protocol/DataTypeKind.uavcan modules/uavcan/dsdl/uavcan/protocol/HardwareVersion.uavcan modules/uavcan/dsdl/uavcan/protocol/SoftwareVersion.uavcan modules/uavcan/dsdl/uavcan/protocol/debug/16370.KeyValue.uavcan modules/uavcan/dsdl/uavcan/protocol/debug/16383.LogMessage.uavcan modules/uavcan/dsdl/uavcan/protocol/debug/LogLevel.uavcan modules/uavcan/dsdl/uavcan/protocol/dynamic_node_id/1.Allocation.uavcan modules/uavcan/dsdl/uavcan/protocol/dynamic_node_id/server/30.AppendEntries.uavcan modules/uavcan/dsdl/uavcan/protocol/dynamic_node_id/server/31.RequestVote.uavcan modules/uavcan/dsdl/uavcan/protocol/dynamic_node_id/server/390.Discovery.uavcan modules/uavcan/dsdl/uavcan/protocol/dynamic_node_id/server/Entry.uavcan modules/uavcan/dsdl/uavcan/protocol/enumeration/15.Begin.uavcan modules/uavcan/dsdl/uavcan/protocol/enumeration/380.Indication.uavcan modules/uavcan/dsdl/uavcan/protocol/file/40.BeginFirmwareUpdate.uavcan modules/uavcan/dsdl/uavcan/protocol/file/45.GetInfo.uavcan modules/uavcan/dsdl/uavcan/protocol/file/46.GetDirectoryEntryInfo.uavcan modules/uavcan/dsdl/uavcan/protocol/file/47.Delete.uavcan modules/uavcan/dsdl/uavcan/protocol/file/48.Read.uavcan modules/uavcan/dsdl/uavcan/protocol/file/49.Write.uavcan modules/uavcan/dsdl/uavcan/protocol/file/EntryType.uavcan modules/uavcan/dsdl/uavcan/protocol/file/Error.uavcan modules/uavcan/dsdl/uavcan/protocol/file/Path.uavcan modules/uavcan/dsdl/uavcan/protocol/param/10.ExecuteOpcode.uavcan modules/uavcan/dsdl/uavcan/protocol/param/11.GetSet.uavcan modules/uavcan/dsdl/uavcan/protocol/param/Empty.uavcan modules/uavcan/dsdl/uavcan/protocol/param/NumericValue.uavcan modules/uavcan/dsdl/uavcan/protocol/param/Value.uavcan
[ 7/14] Creating build/px4-v2/ap_version.h
[ 8/14] CMake Configure px4
[ 9/14] PX4: Copying rc.APM to px4-extra-files/ROMFS/init.d/rc.APM
[10/14] PX4: Copying rc.error to px4-extra-files/ROMFS/init.d/rc.error
[11/14] PX4: Copying rcS to px4-extra-files/ROMFS/init.d/rcS
[12/14] PX4: Copying px4fmuv2_bl.bin to px4-extra-files/ROMFS/bootloader/fmu_bl.bin
-- nuttx-px4fmu-v2-apm
-- could not find gdb
-- could not find gdbtui
-- Configuring incomplete, errors occurred!
CMake Error at cmake/toolchains/Toolchain-arm-none-eabi.cmake:62 (message):
  could not find genromfs
Call Stack (most recent call first):
  /usr/share/cmake-3.5/Modules/CMakeDetermineSystem.cmake:98 (include)
  CMakeLists.txt:204 (project)


CMake Error: CMAKE_ASM_COMPILER not set, after EnableLanguage

[13/14] CMake Build px4 msg_gen
make: *** No rule to make target 'msg_gen'.  Stop.

Running from the source directory

Validation skipped for /home/prince/ardupilot/modules/mavlink/message_definitions/v1.0/ardupilotmega.xml.
Parsing /home/prince/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.
Note: message DEVICE_OP_READ_REPLY is longer than 64 bytes long (143 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DEVICE_OP_WRITE is longer than 64 bytes long (187 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /home/prince/ardupilot/modules/mavlink/message_definitions/v1.0/common.xml.
Parsing /home/prince/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 (80 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 (189 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 (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 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 FOLLOW_TARGET is longer than 64 bytes long (101 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 GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 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.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED 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 LOGGING_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 LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /home/prince/ardupilot/modules/mavlink/message_definitions/v1.0/uAvionix.xml.
Parsing /home/prince/ardupilot/modules/mavlink/message_definitions/v1.0/uAvionix.xml
Merged enum MAV_CMD
Found 208 MAVLink message types in 3 XML files
Generating C implementation in directory /home/prince/ardupilot/build/px4-v2/libraries/GCS_MAVLink/include/mavlink/v2.0/ardupilotmega
Generating C implementation in directory /home/prince/ardupilot/build/px4-v2/libraries/GCS_MAVLink/include/mavlink/v2.0/common
Generating C implementation in directory /home/prince/ardupilot/build/px4-v2/libraries/GCS_MAVLink/include/mavlink/v2.0/uAvionix
Copying fixed headers for protocol 2.0 to /home/prince/ardupilot/build/px4-v2/libraries/GCS_MAVLink/include/mavlink/v2.0

WARNING: Unable to load XML validator libraries. XML validation will not be performed

Waf: Leaving directory `/home/prince/ardupilot/build/px4-v2'
Build failed
 -> task in 'px4_msg_gen' failed (exit status 2): 
	{task 140702271472896: cmake_build_task  -> }
['/usr/bin/cmake', '--build', '/home/prince/ardupilot/build/px4-v2/modules/PX4Firmware', '--target', 'msg_gen']

Thanks for the help in advance.

Posts: 1

Participants: 1

Read full topic

@UASOPJim wrote:

Greetings everyone! I have been excited to use realflight 8 with ardupilot recently and want to get my setup up and running. I have a question though regarding the realflight_quad param file mentioned in the wiki documentation instructions. It does not show up on the recent version of mission planner (1.3.59.3). It is not viewable in the drop down list. I noticed it is not included in the MASTER_SITL folder that one can download for different real flight models. Would anyone happen to know the location of the realflight_quad param file? If so could you point me in the right direction. Thanks in advance!

Posts: 1

Participants: 1

Read full topic

@knightscape wrote:

Hi, folks, I’m a new user, and new flyer, working on my first F550 hex clone with Pixhawk (white case), ArduCopter 3.6.1 Hexa. I’ve been bashing my head against the bench for the last several days chasing down a bad logging error on pre-arm with an occasional accompanying “No I/O thread heartbeat” message. I had been disabling it for testing until it was my last configuration error (I had bigger fish to fry, errorwise). I tried several SD chips that work in other devices, and bought a couple brand new ones tonight. None of those made a lick of difference, nor did any change I made to the the logging bitmask or logging backend settings. In desperation I decided to flash the firmware again to the pixhawk, and during the process accidentally clicked no on “Upload ChibiOS”. The firmware completed it’s flash, and I figured I’d try it out anyway. Started it up, and this time no logging warning. Armed up, throttles go, and we’re “flying” on the bench with no props. Can someone correct me if I am wrong but I believe what I did by accidentally denying ChibiOS was to load NuttX to the pixhawk? If that’s what I’ve done, it seems to have solved an issue plaguing me for the last three days. I powered everything down and pulled the card, and sure enough, I’ve got logs of my stationary flight. Have others run into this issue between ChibiOS and NuttX? In searching causes for this it seems like everyone says “try a new SD chip” and that works.

Posts: 1

Participants: 1

Read full topic

@Kravos1 wrote:

Back story I have a skid steer boat with a 3dr pixhawk running 3.0.1 ardurover. Everything was set up and working correctly. All movement was controlled by the right joystick.

I’m now setting up the pixhawk cube, with 3.4.2 ardurover firmware. I’m trying to set up skid steer and it’s not working. I have 2 thrusters with 2 escs plugged into 1 and 3. Set up servo output with throttle left and throttle right on 1 and 3 like the skid steer set up says. I also have skid steering parameter set as 1. Servo output 1 is the only receiving movement. Output 3 is full throttle and doesn’t move.

Is there a way to mix the channels to have skid steering off one joystick?

Thanks in advance!

Posts: 1

Participants: 1

Read full topic

@AlexP wrote:

Several Youtube videos demonstrate how to connect a Parrot Flypad bluetooth controller and use it as a conventional joystick pad.
In short: connect your Flypad to your laptop with an ordinary USB cable. Do NOT switch the Flypad, and it will behave as a USB device with axes and buttons.
However, in my experience, it stops working after about 2 minutes or so. What shall I do?

Posts: 1

Participants: 1

Read full topic

@bandofpv wrote:

Hello,

I just flashed my Pixhawk 4 with Copter 3.6.1 using Mission Planner. However, when I connect the battery to my power module, I don’t get a voltage reading. I wired up my Pixhawk properly according to this Document. I have also read this article about how to set power modules in Mission Planner. Here is what my screen looks like, indicating no voltage readings:

Mission_Planner_Power_Module_error.PNG1184x860 75.4 KB

I tried different batteries to ranging in different cells and capacitance.

I know it isn’t a hardware issue because when I flashed the board with PX4 using QGroundControl, I get proper readings. Here is what it looked like:

Screen Shot 2018-11-13 at 5.32.19 PM.png2880x1644 589 KB

Is this a bug in Ardupilot or Mission Planner? Or am I not setting it up properly?

Thanks!

Posts: 1

Participants: 1

Read full topic

@nawaratwrn wrote:

I use copter 3.5.7 with 13kg quadrotor designed for carry load of 10kg for sprayer application.
I experience once in a while (not all the time) altitude drop without any reason.
At the time of happening, there is almost no load. So, the power of the copter is very overpower.

I experience this both with lidar and without.
with lidar - I experience once in Loiter mode.
with barometer - I experience it twice in Alt hold mode.
And I cannot really exactly reproduce, it is randomly happen.

From the log, I see
The barometer and lidar detect correct altitude.
But the CTUN.DCRt go negative without any reason at the point of sudden altitude drop.
So, the rotor go down.
We did not give any input to lower it.

In the flight with lidar, when I see the altitude drop, I boost the throttle up to compensate it.
But in the flight with barometer, the altitude drop make the vehicle get down and is already on ground, so, I disarm it.

Note that: the zoomed time is quite not correct, but this is the graph at the incident

The lidar flight, the incident is at 15.18
https://drive.google.com/open?id=1gWR_U-RvewTcIjvCIWmvTdSdsI54ZV8L

Attitude_drop_withLidar.png1920x913 25.7 KB

The barometer flight, the incident is at 14.15
https://drive.google.com/open?id=1_5qDHu5Nwzb8XLcSAUbDhqPyc24fuo-X

sudden_altitude_drop.png1920x889 24.8 KB

Posts: 2

Participants: 2

Read full topic

@R_Q_Robert wrote:

Hi All

I am using Pixhawk 2.4.8 on my 400mm Quad.
I have recently update the firmware to Copter 3.6.1.

I have found these parameters ATC_INPUT_TC and SERVO_OUT.
I am not sure how to set these Parameters, any can help me would be greatly appreciated?

Posts: 1

Participants: 1

Read full topic

@Tomoki_Adachi wrote:

I am planning to make it fly without using a magnetic compass.

I am using moving base rtk to compute yaw angle with a companion computer.

However, I do not know how to send yaw angle to pixhawk and which program should use yaw angle of rtk．

I hope someone tell me．

Thank you!

Posts: 1

Participants: 1

Read full topic

@Tomoki_Adachi wrote:

I would like to do flight control without using a magnetic compass．

In the companion computer, it was possible to calculate the yaw angle using movingbasertk.

However, I do not know how to send yaw angle from companion computer to pixhawk, and which program should be fixed．

I hope someone tell me.

Thank you!

Posts: 1

Participants: 1

Read full topic

@JadeLogan wrote:

My question is: can Serial 4, ie the FrSky, port on Pixracer be configured to accept a GPS unit?

I’m running ArduCopter v3.5.7 and cannot connect a GPS to Serial 4 although the serial mapper indicates I can configure Serial 4 to be a MavLink port, GPS, FrSky, etc.

I’m following the pinout for Serial 4 from
https://docs.px4.io/en/flight_controller/pixracer.html

• Jade

Posts: 1

Participants: 1

Read full topic

@victole wrote:

Hi guys,

I have a Pixhawk from Radiolink and always in every first attempt of armed I get the error “PreArm: Gyro Inconsistent”.

The most strange thing is that i’m using only the external gyro+compass. i disabled the internal to avoid this issue. Also

• I tried to recalibrate the gyros at least 5 times.

• I changed the firmware version from the latest to the 3.8.53 because i have a friend with the same board and he does not have issues with this firmware version.

But i have the same behavior

If i disconnect the battery and connect it again on second time the pixhawk arm without any issue.

Wondering if it could be a good solution to disable the INS pre check. Or try disabling SKIP_GYRO_CAL

some help will be very welcome

Thanks in advance

Posts: 1

Participants: 1

Read full topic