Dear Community,
I am facing a decent problem. My drone, became almost uncontrollable, because of weired RC-Inputs.
Situation: I am using this setup for almost 1 year without any bigger issues. But last week the drone received or interpret strange RC-Inputs, which you can see in the logs. It changed the flight modes rapadly and randomly. Same for the other channels, like pitch, roll,yaw,kill switch… I don’t know if I am facing the same problem as other users.
Other topics:
opened 07:09AM - 05 Jun 18 UTC
closed 06:25AM - 18 Jun 18 UTC
Using Pixhawk 4 autopilot with 1.8.0 beta-2 (ab279d5f) firmware, testing mc02 te… st card which is a full autonomous mission.
The vehicle took off and started to follow the mission, after waypoint 4 the vehicle fell out of the sky.
<img width="816" alt="px4fail" src="https://user-images.githubusercontent.com/5013954/40960333-3a5b118a-6854-11e8-9657-2c6aecbf5933.PNG">
The mission was started from QGC and the RC throttle was at the minimum, the log shows that after 10:09 the vehicle changed flight mode to stabilize and fall due to the low Throttle.
The question is why the vehicle exited mission and changed to Stabilize?
Should the vehicle hover, change to altitude or any other option instead of changing to Stabilize when the mission is aborted?
Here you can find the log
https://review.px4.io/plot_app?log=51293c49-2708-4356-b5f2-11c4ca820a3a
and the [tlog](https://github.com/PX4/Firmware/files/2071166/2018-06-04.10-02-44.zip)
Any question please let me know.
opened 06:57PM - 09 Nov 17 UTC
closed 11:27PM - 31 Dec 17 UTC
bug
Multirotor 🛸
**Bug Report**
I file this as a bug report since I'm concerned that my crash … today may have other reasons than accidentally flipping the Kill Switch.
I was performing some tests to eliminate a strong Oszillation when braking in PosCTL. This was improving, when I wanted to do another Test, shortly after Taking of the Rotors stopped in Mid-Air and the Vehicle crashed on the road where Motors where spinning again. While hitting the Ground the Battery got disconnected (as can be seen in the Telemetry log).
Sadly the ULG stops shortly after start so about 2meters of flight are missing from the Vehicles Log (this is kind of strange). Also the OSD did not record anything since it claimed that there was no Communication (this may also be a bug of the OSD FW but it said that there was no data for more than 400 secs, which usually does not happen).
So I'm stuck with the Telemetry Log. This is the last I got over Telemetry (from the Log):
Here comes the 2nd strange Part. The Kill-Switch was engaged and disengaged under **0.5 sec and this twice in sequence**. I checked with my Remote and it is almost impossible to really push the switch to the position in-between where it may flip back in this quick manner. I'm not aware that I flipped the Switch and the Telemetry RC Input (Channel 6) does not reflect any change in Signal. I performed many flights, and never flipped the switch unintentionally.
Telemetry Log (Check last 15 secs) : [2017-11-09 18-05-27.tlog.zip](https://github.com/PX4/Firmware/files/1458838/2017-11-09.18-05-27.tlog.zip)
ULog Upload : https://review.px4.io/plot_app?log=1452c840-3003-4913-b528-1fff3f17d447
@tridge : You wrote, that you are working with “Arthur from Holybro” on this issue. In post #4 you mentioned, that the IOMCU (a STM32F100) is responsible for SBus parsing and that the firmware is identical to the one used for copter stable...
Back in August, using AC 3.6.0 RC7 on HolyBro’s Pixhawk 4 I had a weird crash on the country side in northern Germany. After some successfull flights, during another flight I suddenly lost control over the copter. It started doing weird things and...
Reading time: 11 mins 🕑
Likes: 21 ❤
Thanks
