testing of focus, orbit and follow
I went out yesterday playing with focus, orbit and follow. I unfortunately forgot my notebook to write down test results so I am not 100% sure which program I had a RTH problem with. I am 80% sure it was the Orbit program. I was testing various things like taking over control of the drone in mid flight. Everything was working fine until my battery became low and the drone initiated RTH, the problem was that the RTH was not a good site for the drone to go to 140 ft and then down, I would have landed in trees. I believe that I hit the RTH button on the controller, since it is not available on the Dronelink screen. I have done this several times before using DJI Fly but not using Dronelink, and I never had a problem. It was like playing tug war with the joystick. I would pull the stick down and the drone would slowly come down but when I let go of the stick it would rapidly head back up. I was only about 30 feet in the air and about 30 feet away so I wasn't too nervous. I finally shut everything down on my phone and muscled the drone down.
Now the second problem. Today I thought I would try to re-enact the same scenario with a better RTH just in case and this time bring a notebook for documentation. The Dronelink program would not go past the start up page with my name. I tried several ( 6 to 8) times to no avail. I tried shutting everything down on phone, even re-started the phone (Samsung S9), I could not get the program to run, DJI Fly worked fine. I was going to re-load the program but thought to write this first. Any ideas??
Comments
7 comments
RTH is functionality that is built-in to your drone and Dronelink has no control over it. You can always override RTH (just as if you were flying in DJI Fly or FJI Go), by flipping the flight mode switch, or pressing the RTH button again on the RC.
What version of Dronelink are you on?
The latest version that was available last week. I can't tell you because I can't open program. Now it go beyond the Dronelink page. I looked under apps and it said 2.4.2 but it doesn't say what build. I think it was 256. I had the gray screen last week and I downloaded the latest build you told me about.
Try build 2.4.1 (156)
I don't see a way in the app store to choose a way to go back. All that's offered is 2.4.2. I downloaded it anyway and same results. But why would it work yesterday but not today?
If you want to install the current production version (2.4.1) you have to opt-out of the beta for now.
How do I get the 2.4.1? How long would I have to give up Beta?
Like I already said, you have to opt-out of the beta.
We don't give release date estimates for new versions so you just have to wait until I post that we fixed the issue.
Please sign in to leave a comment.