randy.sauder
lvl.4
Flight distance : 872572 ft
Canada
Offline
|
randy.sauder Posted at 2017-3-18 21:06
Just noticed this...(in addition to my last 'update' of my saga...)
While Go4 was displaying the "Checking Server/Comparing" message, I went into the app settings and it says that I have the correct fw (e.g. "Latest Firmware!") then I went back to the Go4 home screen and the message updated and indicated "New fw available!".
Ho-Lee-Crap. I've fixed my problem....11hours and 9 min of HELL.
I now have verified 99.999% that all the issues I've been reporting today across my several posts are solved; boy did I learn a lot. I'm not one to give up trying, was just about to go to bed when something clicked. Let me share my fix and a few of my discoveries that will hopefully help others...
Note: Prior to the below info, Go4 @ 4.0.5 / latest and RC, Mavic and Battery was on .400 fw without any issues (other than all the bugs and general flakiness of it)...
Primary Issue: Mavic status (rear) LED fast flashing yellow, No Fly warning with RC connected to phone/app.
Root Cause: Firmware update to .500 failed
Secondary issues I noticed (possibly and likely related and/or I discovered during my journey :
a). The RC and the Mavic are extremely sensitive to the quality of cable you use. While connecting to the Mavic to PC to use Assist2 noticed several times communications were interrupted; I also experienced same issues with high quality ($) cables so this issue is due to the quality of the Mavic and RC's USB ports themselves.
b).DJI Assistant2 PC program is probably a lot better to use than Go4 App for Firmware updates. FW can go corrupted with loss of signal; In my experience this originated from the USB port on the Mavic and RC. However a hickup in one's WiFi can be the cause; In my case I ruled this out with lots of experimentation; for this reason I highly recommend the DA2 software vs WiFi updates.
c). Assist2 program has it's issues; it is not stable as many programs are. I experienced SEVERAL glitches within the program; mostly USB connection drops but also several fails with some calibration routines (the stage failed to load the circle pattern on screen and required having to click back and/or restarting the program. Assist2 had tons of issues within Windows 7- but I found this NOT to be DJI's fault. I traced this issue to a couple drivers that did not install correctly during the Assist2 program installation under Windows 7; the cause for this turned out to be Microsoft disabling and/or delaying 'Automatic Updates" for Win7 (since they are phasing out W7 in favour of Win10). This caused me to move my installation and use of Assist2 under a Win10 installation. After installing DJI Assist2 under Windows 10, there were no driver issues!
d). DJIGo4 App. I eventually reinstalled this to ensure version 4.0.5 was installed as I couldn't verify via Play Store that current version was 4.0.5 (they don't publish this- shame on Google!). This was precautionary...I don't have any evidence that this in itself fixed anything. The app did report that my firmware was successfully installed, then indicated that New Firmware was available multiple times. Many times the updating did not succeed. The Assist2 app did complete the updates 'successfully' and much quicker. However the app indicated that the FW was not current, then sometimes said it needed an update (even though in the settings it would say "Latest Firmware!". Very Very flaky! Bad DJI! Bad.
So I am really tired now so I'm going to cut to the case the explain what my 100% FIX was.
I finally suspected that maybe I should ignore the Firmware update failed warnings etc and focus on why at some point did my RC get stuck in "Connecting.." e.g. not ever connecting to the Mavic. This got me to thinking about my other hobby - RC helis. My theory was "maybe the RC isn't binded to the Mavic". I looked this up in the manual and followed the directions to re-bind the controller to the Mavic. One should never have to do this. The binding indicator light before I did the re-bind procedure was already green. However when I did the re-bind........100% connection restored....also my fast flashing yellow LED turned normal green blink. RC was 100% connected with full GPS lock!! Rebooted all devices and perfect startup all around. IN FACT AFTER REBINDING THE RC TO THE MAVIC ALL THE FIRMWARE UPDATE NOTICES/ERRORS ECT DISSAPPEARED! There was no firmware issue at all as a root cause.
My theory is that the first firmware update failure caused my RC to un-bind to the Mavic; however the bind status was always GREEN. Once I reinstalled the firmware, all that I needed to do was rebind the RC and the FW errors then disappeared! Fair to note that DJI's User's Manual for the binding procedure is lacking with some minor errors that might confuse some people; no biggie but incomplete.
If the above theory is incorrect there is only one other possibility, and admittedly I can't rule out. It is possible that early on when I was having firmware issues, that when scrolling through the options in the Go4 app, that I mistakenly touched my finger across the "Link to RC" option that is located at the bottom of the menu withing I think camera settings. This may actually UN-link/bind the RC to the Mavic causing my RC never to regain connection to the Mavic until I re did it later...10 hrs later. By fluke. It is noteworthy that re-binding the RC 100% cleared every firmware failure and update notice. This I am 100% certain of. But I don't dare experiment
So freaking mad and happy at the same time so I'm opening a $200 bottle of Tequila to help me sleep now. Can't wait to fly my Mavic tomorrow!!!! |
|