Hi everyone
Last day I was performing an auto mission when Pixhawk changed suddenly from AUTO mode to ALT HOLD. No, I didn´t give any input to that and there was no failsafe activated to blame.
Only thing I see at the log is RC error messages, but in auto mission this shouldnt be any problem.
MAVlink communication between Pixhawk and a Raspberry was on use during the flight, don´t know if it can be related.
Any help could be appreciated. I leave here bin file.
Thanks in advance!
Replies
The screenshots are from APMPlanner2 , the best GCS for log analysis, especial when you learn the power of presets and graph groups..
you can see if there is a better firmware, and/or a changelog that indicate they fixed an issue with incomplete dataframes being output.
It is a FrSky X6R receiver for a Taranis X9E emitter. Lot of problems in late times, loses RC connection at a very close distance.
What program do you use to analyse the logs? I use the own Mission Planner, but don´t look as clear as this one you do.
Andre K. said:
Ok I see it now, thank you very much. I still don´t know why at second 47 RCIN3 signal recovered but RCIN5 no, but it is an advance.
What program do you use to analyse the logs? I use the own Mission Planner, but don´t look as clear as this one you do.
Thanks!
many of your channels, including RC1, remain at "failsafe value" of 874, it's a if your receiver partialy recovered, but did not got them all.
I would throw it away, what brand is is ?
Late reply because I am on vacation.
When you lost RC signal, RCIN.C5 was AUTO mode , PWM 1545us
When RC were recovered for a while (see RCIN).C3 , then your mode switch were suddenly still at 874us (ALT.HOLD) , as if there were still no signal..
Dear Andre K
Thanks for your answer, but I am not talking about that change. I am talking about the change in second 47 from AUTO to ALT HOLD, wihtout any RC input as you can see in this capture:
Captura.JPG
Seeing you log, you were in RTL mode (commanded by RC) , then switched to ALTHOLD (by RC)
PWM in on RC5 verifies it:
your description does not match the log...