On one of my autonomous vision-landing tests, I got this error on the logs:
setVirtualStickModeEnabled() failed (will retry): Execution of this process has timed out(255)
As a consequence, I lost complete control of the drone using virtual sticks.
I'm not sure what was the cause, but I noticed RosettaDrone was not running in foreground and the mobile screen was off.
Maybe a bug in the DJI's SDK.
It also seemed that the drone was stuck moving with fixed direction and velocity, so I took the RC before it crashed.
After that, I noticed that virtual sticks were not responding any more, while moving with the RC was working fine (as usual).
I googled for the message Execution of this process has timed out and found some reports related with moving the gimbal.
On my tests, I also move the gimbal to -90°:
Describe the bug
On one of my autonomous vision-landing tests, I got this error on the logs:
setVirtualStickModeEnabled() failed (will retry): Execution of this process has timed out(255)As a consequence, I lost complete control of the drone using virtual sticks. I'm not sure what was the cause, but I noticed RosettaDrone was not running in foreground and the mobile screen was off. Maybe a bug in the DJI's SDK.
It also seemed that the drone was stuck moving with fixed direction and velocity, so I took the RC before it crashed. After that, I noticed that virtual sticks were not responding any more, while moving with the RC was working fine (as usual).
I googled for the message
Execution of this process has timed outand found some reports related with moving the gimbal. On my tests, I also move the gimbal to -90°:Gimbal Pos: -90.0 : 3.4028235E38Steps To Reproduce
No idea
Screenshots
No response
Desktop
No response
Smartphone
No response
Additional context
Model: DJI Mini SE