Thanks for your help.
Recently, my drone cannot take off by offboard control mode, once when I completed a flight by offboard control and wanted to start the second flight.
There is the warn and error in the terminal of the Jetson TX1, when the drone cannot take off.
I feel confused about this situation.
Because the drone can take off and land by offboard control at the first time, my python script should be fine.
However, at the second flight, the drone cannot take off by offboard control with the same python script.
Besides, the drone still can take off by FrSky RC radio control.
Thus, there is no issue in battery or GPS.
Thank you very much again
Please upload a logfile to logs.px4.io and link it here.
Dear Julian:
Thank you very much for your help.
Since the the pixhawk only records the log when the drone successfully fly, I only have three successful logs at the day, instead of the failed one. Really sorry.
When the offboard control cannot take off or fail, the pixhawk will not record the log.
At the day, I have a three flight log.
The first log and the last log are controlled by FrSky RC radio controller.
The second is controlled by offboard control.
04-06-2023 20:07
04-06-2023 20:14
04-06-2023 20:29
On the other hand,
After observing some previous successful terminal log in Jetson TX1, where running
roslaunch mavros px4.launch fcu_url:=/dev/ttyUSB0:921600
The previous successful terminal log in white.
The failed terminal log in black.
I think the error message or reason may be these lines:
VER: broadcast request timeout, retries left 4
VER: broadcast request timeout, retries left 3
GF: timed out
RP: timed out
WP: timed out
However, I found the similar post but cannot find a solution.
Besides, the issue only happens after the drone completed a flight by offboard control, so the reason should not be wiring or FCU autopilot version.
Thank you very much again
After switch the SDLOG_MODE from 0 to 1.
I get the log, when the drone cannot take off by offboard control mode, when try to take the second flight.
07-06-2023 12:56
07-06-2023 12:57
My temporary solution is to reboot the PIxhawk and computer.
Then, the offboard control can work again.
