Beta test flight no video feed and aborted after take off
Been using Dronelink successfully on a Mavic Mini and a Mini 2 and been looking forward to this release for my Mini 3 pro. Downloaded Dronelink DJI 4.50.0 onto Samsung s10 (android 12) and like some other users concerned about giving DJI full access to my phone, and all its data. So I downloaded it onto a clean s7 64bit (android 8) giving full access. It loaded ok with the warning that being an older device it may have some operating issues. Decided to give it a try and loaded a short local plan, after doing all the checks it gave the ok to fly message but no video feed. Did the usual countdown and took off and hovered and then gave message that the mission had been aborted. Drone flown by manual control still in the Dronelink DJI plan, still no video feed but would record video and take photos using manual control. Decided to try the s10 and give Dronelink DJI access to all the requirements, phone, photos, etc and tried test again. Still no video feed but took off and aborted mission as before and able to take video and photos.
Comments
4 comments
Thanks for the feedback, but these issues have already been reported in multiple other threads.
We all have more or less the same concerns.
Hi Jim, thanks for coming back so quickly, always been delighted with Dronelinks ability and the work you and your team do to get these programs up and running despite the delays you experience in getting the MSDK. I appreciate others are having the same problem but just wanted to feedback on my experience as part of the beta program using both the s7 and s10 incase there may have something in my comments that help. Please keep up the good work you do in supporting your customers
Hi Jim, Been doing some research and further testing of the beta program with some results on the lack of video feed which may help. I have been doing all my flying using the RC-1N controller using a Samsung s7, s10 or mini iPad for the Mini 2 and the MINI 3 pro. Dronelink worked fine on the Mini 2. Three weeks ago I purchased the RC controller for ease of use. However on the first flight of around 50 meters it disconnected 3 times while taking photos. I did a check to ensure all the settings were ok and did a second flight and again it suffered 2 disconnects so I returned it thinking it was faulty. Through further research on the RC controller there are a number of posts suggesting taking photos using the 48mp setting could be the possible reason due to a processing time of up to 8 seconds. It set me wondering if there was any connection between the problems on the RC controller and the loss of video feed when using the beta program on the RC-1N. I loaded and opened the program using the s7 phone and as before there was no video feed. However I switched between the various camera modes and on High definition got a live video feed but it froze after about 8 seconds. I then tried AEB and again got a live video feed which lasted longer but on single frame or video there was no feed and just a black screen. I tried AEB and high definition again and was able to take photos by tapping on the screen button. I decided to try flying a mission in the AEB setting. All the data looked good so on launching the mission the drone took off and hovered before I got the message ‘unable to take control’ and the mission stopped with a manual flight message in a green box at the top of the screen. The drone flew normally but the screen was frozen so I started switching between camera modes and got a live video which lasted varying times from around 4 seconds to around 3 minutes in AEB mode and I could take photos manually I also tried timed photos at 10 seconds and this worked fine. If I tried video or single photo I simply got the black screen. I was able to use the camera gimble and zoom in certain modes. The photo/ video button made the normal sound but did not take pictures. Sorry about the long post but hope it might help you.
Please sign in to leave a comment.