@rijun034 wrote:

It is very sad to say that my Skywalker X8 flight got crashed.

Incident:

Hand Launched. Used only Throttle stick.
Plane started to glide and suddenly it rolled left and crashed.

After crash I checked my Control surfaces and it’s perfectly configured.
I used FBWA mode and it worked.

After checking the logs I found that both Compass and Magnetometer got failed.
I’ve successfully did all the calibration and the plane got Armed after all.
My CG and weight balance was fine.

My analysis:
I’ve enabled EKF in mission planner parameter and I did my Mag calibration successfully. But I don’t know what happened really.

I attached my log file links (https://drive.google.com/open?id=1LZyPhObXW30uKauDdFdQc6oHD91hzYSa) https://drive.google.com/open?id=18hPlAPL9uKtd4jqApMaDsiBtLAvjKSY5. Hope someone can understand and can help me out of this problem.

Posts: 2

Participants: 2

Read full topic

@Taipan wrote:

I am in the process of fitting an Omnibus F4 Pro flight controller to a Bixler 3 and I need to make sure that the flight controller board is mounted “level” with the Bixler 3.

I assume that when the Bixler 3 is trimmed correctly and cruising at a steady altitude, that the stabiliser is “level” (perfectly horizontal) and thus the flight controller board needs to be perfectly parallel with the stabilser/elevator to maintain a constant cruising altitude?

Is that correct?

Posts: 7

Participants: 3

Read full topic

@martinlta wrote:

Hi
I have installed ArduPlane v3.9.1 on an Omnibus Pro F4 v3. I have soldered the ppm PPM solder pad/resistor and in Mission planner I haver RC inputs from the receiver(R9 mini sbus out) with TX is Taranis xd9 plus (mode2.). However on the mission planner radio calibration, the inputs are mixed up. Throttle is responding to the left rudder on the TX and elevator on the TX makes the pitch move. I have tried changing modes on the TX etc but are getting nowhere ?

With previous a Omnibus Pro F4 v3 (sbus pad/resistor soldered) using INAV I never had this input mix up issue with the radio inputs?

Posts: 2

Participants: 2

Read full topic

@artemen wrote:

Been using aircraft in question with AP3.9.1 since it was released (20-30 flight hours) without any issues.

Updated to 3.9.2 a week and a half ago nothing else changed. First flight on AP3.9.2 resulted in crash while in RTL mode.
Took off in FBWA, got up to speed, engaged RTL, did 1 successful turn, on the second it stalled, rolled 180, recovered, started 3rd turn, but stalled again, this time it was about 1-2meters above the ground so crashed. After going through the log, I noticed that airspeed logged 2-4m/s which is waay low, as stall speed is 8m/s and I clearly remember plane was flying and climbing. I checked i2c airspeed sensor and found that VCC wire was broken under insulation and making sporadic connection. Fixed the issue, check other wires.
LOG#1

Today, still at 3.9.2. All pre-flight checked out good. Took off in FBWA, got up to speed 20m/s+ verified through OSD, engaged RTL. This time plane rolled 180 at the first turn attempt but recovered, than attempted 2nd turn and recovered again. At this point I’ve switched to FBWA, but was too far to see orientation clearly, so while getting googles on lost airspeed and stalled again, At that point I’ve killed throttle and put the plane into a field as it was getting too close to a public road.
LOG#2

I think that maybe some parameters changed after the update process, or maybe there is some other issue, but RTL at 3.9.2 clearly overshoots roll angle, while at 3.9.1 it was a great flier.

Any input is much appreciated!

Posts: 2

Participants: 2

Read full topic

@tridge wrote:

ArduPilotPlane.jpg750x291 33.1 KB

This is the first beta release for the 3.9.3 firmware. This release
has the following changes over 3.9.2:

• fixed error handling for corrupt RC input that could lead to a
  crash in unusual circumstances (I don’t believe this has actually caused any crashes, this was discovered during code review)

• fixed a race condition in IOMCU event startup that could lead to
  the safety not being disabled on boot with BRD_SAFETYENABLE=0

• ensure surface speed scaling covers full range of configured
  airspeeds

• added builds for new boards F35Lightning, omnibusf4v6, mRoX21-777

• updated GPIO numbers on AUX pins on all boards to be consistent
  with docs

• updated KakuteF7 UARTs and buzzer

• added ESC sensor uart on OmnibusNanoV6

Happy flying!

Posts: 1

Participants: 1

Read full topic

@hangarspace wrote:

I’m putting together a Matek F405 Wing with ChibiOS Arduplane, and yesterday I looked at adding an analog airspeed sensor. I’ve previously used these on APM’s and digital ones on Pixhawks with great success.

So, this is an analog sensor connected to the rssi pin (15). I have made the settings as per the screen shot and the board is flashed with version 3.9.2/October 12th.

Since it isn’t fitted in a model yet, I’m just testing it by blowing in the end. The really odd thing is that as the airspeed changes so does the pitch! The F405 board is not moving at all, I am firmly holding it on the bench.

Also, if I disconnect the sensor from the rssi pin, the artificial horizon in mission planner pitches down and then recovers to level after a few moments, and if I reconnect the signal the ah pitches up before recovering.

This morning I un-configured the airspeed and set the rssi to use pin 15/analog, added the rxrssi to the Mission Planner hud. I kept the airspeed sensor connected and blew in the end. As expected, the rssi value changed but the horizon did not pitch either way.

Ideas?

Chris

AS_Pitch.PNG1091x711 13.1 KB

2018-11-05 19-45-26.zip (55.6 KB)

Posts: 1

Participants: 1

Read full topic

@martinlta wrote:

I am looking at tilt rotor plane confguration in the plane docs. Ok with frame class as 7 tricopter. But what is the frame type for 2 motors vectoring up together and a rear motor vectoring left and right with a servo as in a tricopter for yaw

Posts: 1

Participants: 1

Read full topic

@glacier051 wrote:

Hello:

Need a little hand holding here.

I’m building a quad tilt-wing. I’ve flown the frame as a quad, using Copter. I have the latest Plane installed now and the Q functions enabled. What I’m running into is kinda strange.

First thing is I don’t have the wings installed due a 3D printer malfunction, so waiting to get that back to fabricate the wing sections. I haven’t flown it in any of the Q modes yet.

My present flight modes, on 2 separate Taranis switches using “replace”, are:
QLoiter
QHover
FBWA
QStabilize
Manual
QRTL

The tilt servo is on Pixhawk 2.1 Servo9.

On the bench, no props and disarmed, I can get the motors to tilt from vertical to horizontal in both Manual and FBWA. If I arm the frame, Manual gets me full down tilt but FBWA does not. FBWA will twitch the tilt servo but nothing more. The odd thing is if I add THR, the tilt servo starts following it, so that at full THR, the motors are horizontal. Let up on the THR and the motors move back vertical.

The other oddity here is if I flip in and out of Manual while the other Taranis switch is in FBWA, the motors will go full down and stay there.

I’ve read about and changed the Tilt_Assist and Q_Tilt-Max functions, etc. along with the “Arspd” parameters and nothing seems to get the motors to tilt when armed and in FBWA. I’ve even used compressed air to simulate air speed thinking that param needed to see something. Nothing changes Re FBWA.

Also, being new to Arduplane in general, I am unable to get a Taranis radio off failsafe to work. I can invoke a manual F/S and the flight changes to QRTL. I’ve set the Taranis custom F/S to the same value but Mission Planner shows me the last flight mode before turning off the radio. Kinda nervous about flying in that situation.

Build:
-Frame and arms are Home Depot square 15x15mm aluminum towel bar and Actobotics U channel and bearings

• 2.1 Pixhawk
  -Sunnysky X4108S 480KV motors
  -Hobby King CF 15x5.5 props
  -Lumenier 4 in 1 35A ESC/PDB
  -Gopro on a gimbal
  -Old DJI F550 gear struts

When I get the printer back, print up wing ribs and skin with 1/32" balsa, using the square arm tubes as the spar with additional 5x5mm CF tube as secondary. There will be a total of 8 wing sections 2 each per arm in and outside the motors. Aerodynamic controls will be ailerons on the outer front panels and elevators on the inner rear panels. Rudder mounted aft. Wing span looks like 42-48" x 2.

Any thoughts are appreciated.

Posts: 1

Participants: 1

Read full topic

@tucuman79 wrote:

Hi, I search in the forum but i couldn’t find a solution for an issue. When I power up my Pixhawk 2.1 it starts in RTL mode and servos moves continuously, I like to startup my plane with the radio control turned off and wait until it gets gps signal. Is there a way to startup in manual mode or other mode? thank you!

Posts: 4

Participants: 2

Read full topic

@arjun7965 wrote:

Hi,

I am trying to make a simulation model in Xplane 11 or Realflight for an octaplane with 2 forward puller motors (so a total of 10 motors). I just wanted to know if ardupilot supports that. From @tridge’s comment last November, “The main limitation is that ArduPilot can only control 8 actuarors - so if you have an OctaQuad Quadplane which typically has at least 12 actuators then you can’t control all of them from ArduPilot.” Is this still the case or does ardupilot has support for ~12 actuators?

If not, it would be great if someone could guide me in the right direction to get the integration working.

Any help is appreciated. Thank you.

Posts: 3

Participants: 2

Read full topic

@Nihal wrote:

Hi,

My XUAV Talon that has flown for over 30 hours without issue fell out of the sky when performing a corridor mission. There were no changes to the setup. It had flown properly just an hour earlier. It just nose-dived while taking a turn. Any Ideas?

Link to log - https://drive.google.com/file/d/1UGgMNmCAzl5yQg_SjDlvGDeMaoXkiVfx/view?usp=sharing

Thanks!

Posts: 1

Participants: 1

Read full topic

@aziz_kountche wrote:

hello , what happen when i chose quadplane with all four motors tilting ?
in fixed wing mode did the 4 motors run to push airplane forword ? or just the 2 front motors ?

Posts: 1

Participants: 1

Read full topic

@sripad_sahu wrote:

Hello,
I am trying to add new Custom Libraries into the ArduPIlot. So I added all the files to the Libraries folder and then imported all the Libraries from GCS_MAVlink.h. But when I build it for SITL it shows these errors:

ArduPlane/GCS_Mavlink.cpp.22.o: In function GCS_MAVLINK_Plane::handleMessage(__mavlink_message*)': GCS_Mavlink.cpp:(.text._ZN17GCS_MAVLINK_Plane13handleMessageEP17__mavlink_message+0x3dd): undefined reference towc_InitRng’
GCS_Mavlink.cpp:(.text._ZN17GCS_MAVLINK_Plane13handleMessageEP17__mavlink_message+0x3ec): undefined reference to wc_InitRsaKey' GCS_Mavlink.cpp:(.text._ZN17GCS_MAVLINK_Plane13handleMessageEP17__mavlink_message+0x408): undefined reference towc_MakeRsaKey’
collect2: error: ld returned 1 exit status

Any Idea on how to solve it? There are other people with the same question, on how to add a custom library to ardupilot. But those are also unanswered. Basically to sum up , my question is how to add external Libraries to ardupilot?

Thanks,

Posts: 1

Participants: 1

Read full topic

@tridge wrote:

ArduPilotPlane.jpg750x291 33.1 KB

The ArduPilot development team are delighted to announce the 3.9.3 stable release of the ArduPilot plane code. This release includes a number of small but important fixes over 3.9.2:

• fixed error handling for corrupt RC input that could lead to a
  crash in unusual circumstances

• fixed a race condition in IOMCU event startup that could lead to
  the safety not being disabled on boot with BRD_SAFETYENABLE=0

• ensure surface speed scaling covers full range of configured
  airspeeds

• added builds for new boards F35Lightning, omnibusf4v6, mRoX21-777

• updated GPIO numbers on AUX pins on all boards to be consistent
  with docs

• updated KakuteF7 UARTs and buzzer

• added ESC sensor uart on OmnibusNanoV6

• fix for Benewake rangefinder at long ranges

• prevent attempts to erase dataflash logs while armed

Many thanks to the people who tested this release!

Happy flying!

Posts: 1

Participants: 1

Read full topic

@lorbass wrote:

When I want to descend in Loiter Mode by Stick input of Pitch the Wing descend but proportionally to
the difference to the original altitude the THR_OUT increase up to THR_MAX and of course also the speed.
Even when reducing with Throttle Stick down to min. And after releasing the Pitch Stick it climbs
immediately on the original altitude.
In the log the param TECS dhdem remains on its Loiter start value and the Pitch Intput has no
influence on it. As it does in FBWB Mode.
Here the situation:

Analizes Loiter issue.jpg1502x712 113 KB

The Log:
https://drive.google.com/open?id=1WBTw4EdCpFqh4jdZDQ2qHQTw_2AeQihT
And the video with Loiter from 6 min on. Also good to hear like a fighter attack.

I did not test climbing in Loiter, may be even worse (Throttle reduced to Zero?)

Posts: 1

Participants: 1

Read full topic

@Brian_Duvall wrote:

Hello,
I recently figured out how to convert the epoch time from my arduplane data flash logs in matlab. The problem is it looks like I was flying for four days! lol. I know the flight was no longer than 20 minutes. Aafter running the script below I just watch the HH part of the output and I see the hours incrmenting from zero to 24 four times over the flight. I will looking making sure the pixhawk knows the right time I guess.

time_reference = datenum(‘1970’, ‘yyyy’);
time_matlab = (time_reference + GPS_Time)./ 8.64e7;
time_matlab_string = datestr(time_matlab, ‘yyyymmdd HH:MM:SS.FFF’)

Posts: 1

Participants: 1

Read full topic

@saadmir wrote:

I am flying 2000mm wingspan trainer fixed wing with a gasoline engine fitted with Pixhawk Cube (Plane 3.8). Issue I am facing is of Throttle during Auto mode which stays at high always. During descent waypoints specially auto land though altitude decreases but speed gets abnormally high crossing over 45m/s. Cruise speed is set to 20m/s but it never locks on that speed and mostly fly at over 30m/s.

Already done airspeed sensor calibration, even tried disabling airspeed sensor and used GPS alone. Did tuning of pitch and roll but still not getting any success.

Can you advise all parameters that affect the throttle functions just incase i have missed any crtical one.

Posts: 1

Participants: 1

Read full topic

@allen2 wrote:

any though on this will appreciated. im afraid facing another problem again.

Posts: 1

Participants: 1

Read full topic

@JeyPi wrote:

Issue details
If flying Arduplane in Auto mode it is possible to control the mount manually. But only until there is a programmed mission mount command like DO_MOUNT_CONTROL (sets the mount Pitch Roll and Yaw positions, or DO_SET_ROI (sets an area of interest at which the camera stares) I did not try the other mount commands
If such a command is received, the mount moves automatically and the operator can not intrude at all.
The mount automatic movement goes on until some other programmed mission mount command is in line or until a mount command is ended (by the DO_SET_ROI, that has empty fields). Only after this “Auto mount movement ending command” is received, you can operate the mount from the transmitter, even though the lapne is still in Auto.

The mount operator is NOT ABLE to move the mount after the mount “auto move order” has been received from the recorded mission.

If during the Arduplane Auto mode (and after the DO_MOUNT_CONTROL, or DO_SET_ROI
HAVE STARTED and HAVE NOT BEEN CANCELLED by the mission),
is the mode switched to Manual, the mount will stay locked in the last received auto mount movement command and the mount operator would not be able to operate the mount manually.

Simply put:
If the auto mission has started and if the auto mount movement command has been issued and then the mode is switched to manual, before the mount receives the “Auto mount movement ending command”, it will stay locked in the last received auto mount movement command and the mount operator would not be able to operate the mount manually. This is most probably a bug in the Arduplane software as I think if the plane is switched to manual mode the mount should leave the auto mode as well.
Or maybe it is there on purpose?
I made this video [https://www.youtube.com/watch?v=aTSBklL3O6A]
to confirm for myself the above behaviour.
The whole flight was done in Auto mode since the takeoff, until the landing. The only manual input was at the end when I operated the camera mount after the “auto mount movement ending command” was received, while the plane was still in Auto mode.
I placed three ROI (Region Of Interest) in the mission and let the Pixracer’s Arduplane cooperate with the Storm 32 board to move the 3D Mobius camera mount, framing the ROIs. to my satisfaction.
Version
Arduplane 3.8.4
Platform
Plane
Airframe type
motorised glider
Hardware type
Pixracer,
Logs
Will add one if needed. This situation is easily reproduceable

Posts: 1

Participants: 1

Read full topic

@RogerR wrote:

Flew an auto mission the other day and the plane went crazy. After hitting a few waypoints, it erratically headed in the wrong directions for about two minutes. I switched to RTL and the erratic course continued. After a couple more minutes, I switched to FBW-A and landed.

Replaying the mission from the tlog, there are many warnings about compass errors. However,as this graph shows, the two compasses (read and green lines) track each other well and move consistently. But the ATT.Yaw value (yellow line) suddenly jumps about 140 degrees (with an "EKF2 IMU0/1 aligned to GPS velocity message) and stays divergent for about 20 seconds. It then follows the compass heading for ~15 seconds and jumps again (140 degrees with an "EKF2 IMU0/1 switching to Compass 1), diverging for another 20 seconds. The IMU eror messages stop, but sudden divergence from the compasses continue for the rest of the flight.

image.png1536x362 13.1 KB

The log for the flight can be downloaded at https://drive.google.com/open?id=102XR-aZ_ghyLry_TV-1uHo0xI6J0yg80
What should I look at next?

Posts: 9

Participants: 2

Read full topic