Hello everyone,
I had a strange incident today while flying, and I’m looking for feedback.
My setup:
The problem:
While in flight, my transmitter announced “Landing” over the speaker, even though I was flying normally and the radio link seemed fine.
Does anyone have any idea why this happened?
I think it is a little bit less information about your “incident”.
At minimum are the .bin logfile of the flight is required.
Yes I can share the .bin logfile, I haven’t see the error: https://storage.to/K8VVBQL1q
According to the log file, the flight was uneventful. The voice announcement from the TX16 may be related to EdgeTX or ExpressLRS settings or scripts on the TX16s ?
Rolf
Over the years I’ve had random call outs from Yaapu and I’m using the same hardware as you are. My suggestion is to make sure everything is up to date. The random call outs were more common in the past and I don’t notice them nearly as often any more.
The Nomad module is typically a transmitter. Are you running yours as a receiver on the drone or do you have something else on the drone?
Are you running your ELRS system in Mavlink mode?
I get the bad battery 2 voice with Yaapu on my RadioMaster TX16S in the past even know i not using bat 2. Can’t recall if i gotten it lately.
yes in MavLink mode
Yes the Nomad is used like transmitter, the receiver is the XR4, I fix in the first post.
Unfortunately, this afternoon, the aircraft (VTOL) crashed, and I don’t yet know the reason.
Takeoff in QLoiter mode: the aircraft climbs without any problems, then suddenly becomes unstable. It starts spinning rapidly from side to side and seems to have trouble stabilizing. Then, it slowly drifts backward.
I then tried to switch to FBWA, but canceled the maneuver because I decided to land instead. So I switched back to QLoiter, and at that point, the aircraft began spinning in place while descending, with its nose pointed toward the ground.
Here are the logs:https://storage.to/0bm9eJSge (the home position is correct)
I use the Yaapu script, maybe but don’t know
I’ve experienced this when the flight controller is very busy.
Check PM.Load in logs.
A common cause is too much filtering configured, or live FFT, may even need to disable an IMU to run less EKF lanes. example: running octocopter on an older flight controller.
I didn’t find anything in the logs—maybe I’m not analyzing them correctly.
The second log, the one from the crash, doesn’t show anything; it seems like it didn’t record anything.
This is really annoying—I can’t figure out why it crashed like that. I ned to rebuild the plane it before I can test it again.
I will upload the yaapu log tonight
log of flight day previous crash: Log
log of crash: Log
yaapu log crash: Log