EdisonW1979
Second Officer
Flight distance : 1535679 ft
Canada
Offline
|
@Brantel,
As I just eluded to in my response to @hallmark007, the new MA has just experienced the same yaw issue as the last unit, on only it's third flight...
I performed a precision takeoff to 20ft, in a completely open area with no interference points, calibrated compass, and 19 GPS sat locks (a new record for me BTW). I let the drone hover for a good 15 seconds, then turned 45 degrees to the right and began moving forward, and all of a sudden the drone started yawing to the left on it's own with my finger off the yaw controls. Once I gave it a snap to the right, it stopped the veering and began operating normally again for the rest of the flight.
So, I managed to demonstrate that the replacement unit began to have the same uncontrolled yaw movement as others have reported. And this is a brand-new unit, freshly updated to 0400 via Assistant 2 1.2.4. Though no where near as severe as I have experienced with the first MA, or as others have shown here, the error persists.
Now I also wanted to address the issue reported here of choppy video transmission or cutouts, so I conducted a little experiment with the new MA...
DJI GO 4 is a shared-platform app (platform refers to the multiple supported DJI products it connects to), and exposes the various feature sets of each drone it connects to at that time. When Mavic Pro owners came into the discussion, despite being panned by the likes of @hallmark007 and others for doing so, I wanted to determine if there was a connection, and sure enough, there appears to be...
When the "Strong Aircraft Interference" warning appears, it's usually accompanied by video signal transmission interruption, and lack of responsiveness from the AC. Now, if this were in fact the case that the signal was being interrupted or lost, the live video feed that gets cached to the device running DJI GO 4 should have gaps or pauses in it, and rudder responses should show signs of irregularities in the video feeds captured on-drone, especially if a breaking maneuver is performed during a transmission interruption period.
What in fact appears to be happening, is the "Strong Aircraft Interference" warning seems to be a false-positive, because there actually is no interference, but rather resource saturation happening on the smartphone due to DJI GO 4, and what appears to be a resource leak within the app, which saturates the memory and CPU of the device, preventing it from keeping up with the live video feed, but still capturing the data and transmitting stick responses. This is why buffered video is smooth as silk, and rudder controls on the video appear normal, because the drone never breaks contact, or even had the signal interfered with; it was the app that was locking up and unable to keep up. This would explain why, for some time, both Mavic Air and Mavic Pro pilots have been experiencing the same issues. It also explains why for some users they receive these errors and disruptions with the drone hovering only 10-20ft away with no other interference sources in the vicinity.
So, at least where the Signal Aircraft Interference warnings are concerned, I do not believe this is a 0400 issue, but rather an app issue. Parts of the firmware from all the supported aircraft from DJI must share the same codebase and API's that are used with DJI GO 4, and this explains why more than one model now experience issues. Also, DJI GO 4 is coded and maintained by a third-party company, and not DJI directly. I personally believe this is a HUGE mistake, as apps of this nature that are maintained by third-parties NEVER work properly with the intended equipment.
OK, that was a long post, but I wanted to get it out there |
|