Loss of video during flight

[Hawkwind]

While flying a Mavic Pro, I noticed a loss of video. All other telemetry looked fine. First the image went to about quarter of the screen, then the video completely went black. I landed, powered down, recycled the power on the UA and still get no video. Thoughts?

 

[Phantomrain.org]

Cable comes to mind immediately .

Phantomrain.org
Gear to fly your Mavic Pro in the Rain / Snow

 

[Hawkwind]

@Phantomrain.org Well..turns out it was the GO app. I restarted the app and the video came back.

 

[lannes]

@Phantomrain.org Well..turns out it was the GO app. I restarted the app and the video came back.

DJI Go4 sounds a bit flakey, I'd deleted and re-install it to be safe.

 

[PHZ]

Was your iPad/iPhone out in the cold for a while? I had this happen in my very first quad flight with an M Pro (and many times since).

 

[Hawkwind]

I did go out into cold weather, but only long enough for the one short flight.

 

[mereflyer]

I also had the same thing happen - probably about 6 or 7 times. I just hit RTH and wait for the sound of the returning drone (if temporary loss of sight happens!)...

 

[Hawkwind]

I also had the same thing happen - probably about 6 or 7 times. I just hit RTH and wait for the sound of the returning drone (if temporary loss of sight happens!)...

Never lost sight of the Mavic. In fact, it was never more than 100ft horizontally from my position.

 

[Thomas B]

While flying a Mavic Pro, I noticed a loss of video. All other telemetry looked fine. First the image went to about quarter of the screen, then the video completely went black. I landed, powered down, recycled the power on the UA and still get no video. Thoughts?

Not enough info to offer much in the way of suggestions... maybe cold, maybe installed memory in your device is not sufficient.. etc, etc...

 

[Hawkwind]

Not enough info to offer much in the way of suggestions... maybe cold, maybe installed memory in your device is not sufficient.. etc, etc...

Like I said, it was the Go app that had a bug, so restarting the app corrected the issue.