Njorl
lvl.1
Flight distance : 1531821 ft
United States
Offline
|
Donnie * Posted at 2017-8-21 04:28
Ok, the video to the I pad is perfect correct ? You may want to inspect the 2 cables from the Vibration board to the Aircraft, these sometimes can become crimped . Be sure to examine them closely . Also make sure the pins are making good contact beween the camera gimbal and the vibration board. In addition to the cleaning you may wish to loosen the 2 phillips head pan screws on the camera gimabl mountplate , this gives it a bit of wiggle room to seat properly ,Just loosen about 1/2 to 3/4 of a turn on each one , just want a little bit of play , not to much .
Also just for grins try recording in 1080 and not 4k and see if that makes a difference .
*** POSSIBLE PROBLEM LOCATED AT BOTTOM OF THIS REPLY!!! ***
but first....
Thanks for all the bits of advice Donnie; much appreciated. OK...to answer your questions...
I did very carefully remove and inspect the 2 cables + ensure good contact. Although they did not appear crimped, they've served for many hours, so I bought new, and replaced them. Next flight still had issue.
Just this evening I took a QUICK PIC to confirm that all contacts are "leaving footprints" on their corresponding contact stripes: they were.
I have not yet tried filming in 1080...I'll try that in the next day or two to see if that might be the issue.
I've tried duplicating the problem on the ground immediately after a flight, but it seems to not record improperly then. I haven't, however, tried to make numerous "on the ground", minute-long 4K recordings in a row right after landing, however...I'll have to try that soon as well.
Regarding the hard landing question...I did have one moment, just before landing, way back on March 19, 2017, where the rig was stationary hovering less than a foot above ground, but a gust of wind pushed the rig down just a little so the camera did just barely touch ground before the arms had fully reached landing position. There was no damage at all upon inspection, and it had no problems recording video for months afterward.
I did test another player on another PC, and on a Mac, and several different card readers, but none helped.
Just this evening I carefully removed the gimbal board (w/ the 2 phillips head pan screws), carefully disconnected the cable, checked & found no apparent issues, then reconnected ensuring good fit. I reseated the gimbal board and screwed back in the pan screws, but not as tight as they were before so as to leave just a little play in it as you suggested.
...hmmmm...just had another thought...so I went back into the iPad Air 2 to see if the Editor in the DJI Go App has any of the messed up recordings AND IT DOES!!!Under 'Album', 'Videos', there appear EVERY VIDEO FOR THE PAST COUPLE WEEK'S RECORDINGS, INCLUDING THE FAULTY ONES!! The iPad is connected only to my home's WiFi, and when i tap on one of the videos I know was FUBAR on the microSD card, it's smaller version plays just fine on the iPad. When I touch the "i" with a circle around it button in the lower left corner of the DJI "Editor" screen, the information pop-up indicates the date/time, equipment, AND that it's "Size" is "1280x720" (not 4K). When I click the faint, light blue "Download original video" button, it pops up with "Connect your equipment to download the videos". If I ignore that advice, and instead tap the "download to iPad" icon (a down arrow pointing to a wide "U" shape) in the lower left corner of the screen, it pops up with "Save video to your device" button. Once I push that, a pop-up states "Saved". Now if I go into "hotos" app, right there is the full 29-second video under "Camera Roll". I then uploaded to Facebook, then downloaded to my PC laptop, and post it HEREin all it's 9Mb glory.
So...could this likely mean it's NOT the X3, but instead an issue w/ either my iPad storage function, and/or the DJI Go App, and/or the July firmware update?
My iPad has 3.26 GB of "documents and data" within the DJI GO App...by far the biggest memory hog on my iPad. Under "Storage" my iPad lists 11.76 GB used, and only 397.9MB Available. Perhaps this is the problem point?
|
|